Build with Drone #3

Closed
Brain wants to merge 0 commits from test-drone into main
Owner

I separated/duplicated the pipelines, because a tag event is not associated with a branch. Therefore, the trigger cannot include a branch filter and a tag event filter.

The trigger

trigger:
  branch:
    - main
  event:
    - push
    - pull_request

is necessary to only run on a push event on main or a PR towards main. Leaving out the branch here, causes two builds for each PR and interferes with the build status report in Gitea.

I removed the -j4 for the moment, because there is nothing to parallelize.

The rsync package is only needed by the make bundle command, so it doesn't need to be installed at the moment.

I separated/duplicated the pipelines, because a `tag` event is not associated with a branch. Therefore, the trigger cannot include a branch filter *and* a tag event filter. The trigger ``` trigger: branch: - main event: - push - pull_request ``` is necessary to only run on a *push* event on `main` or a PR towards `main`. Leaving out the branch here, causes two builds for each PR and interferes with the build status report in Gitea. I removed the `-j4` for the moment, because there is nothing to parallelize. The `rsync` package is only needed by the `make bundle` command, so it doesn't need to be installed at the moment.
Brain added 1 commit 2022-11-22 13:58:33 +01:00
Separate pipelines for PRs and releases
All checks were successful
continuous-integration/drone/pr Build is passing
continuous-integration/drone/push Build is passing
72d0012f33
Brain changed title from WIP: Build with Drone to Build with Drone 2022-11-22 14:07:34 +01:00
Author
Owner

This seems to work.

Next step would be to merge this and see if the build succeeds on main.

After that, a test tag can be created for the latest commit on main to see if the creation of the Gitea Release works.

This seems to work. Next step would be to merge this and see if the build succeeds on `main`. After that, a test tag can be created for the latest commit on `main` to see if the creation of the Gitea Release works.
dancingCycle was assigned by Brain 2022-11-22 14:09:49 +01:00
Member

Hi @Brain,
The main branch builds on my host. The test tag is also there now.

After that, a test tag can be created for the latest commit on main to see if the creation of the Gitea Release works.

Is the next step to create a secret in drone?

Cheers!

Hi @Brain, The `main` branch builds on my host. The `test` tag is also there now. > After that, a test tag can be created for the latest commit on `main` to see if the creation of the Gitea Release works. Is the next step to create a secret in drone? Cheers!
Member

Hi @Brain Can you imagine a reason why there is no release yet? https://drone.wtf-eg.de/FreeFleetManagement/manual/deployments

Do I need to schedule a job?

The Drone.io trigger is enought, itn't it?

Cheers!

Hi @Brain Can you imagine a reason why there is no release yet? https://drone.wtf-eg.de/FreeFleetManagement/manual/deployments Do I need to schedule a job? The Drone.io trigger is enought, itn't it? Cheers!
Brain was assigned by dancingCycle 2022-12-02 12:14:04 +01:00
Member

My local tags not seem to have arrived on the remote. Without a tag present, there is no reason for drone to fire the cites-release plugin. I'll be back when I solved the tag issue.

My local tags not seem to have arrived on the remote. Without a tag present, there is no reason for drone to fire the `cites-release` plugin. I'll be back when I solved the tag issue.
Member

Hi @Brain ,
Also my second test tag did not apear in the remote. That confused me. I learned that there is the following switch and I tryed it.

git push --tag

That triggered git to push my local tags to the remote. Do you know if that is a gitea or gitea configuration specific behaviour? I did not observe such behaviour in github or gitlab yet.

Cheers!

Hi @Brain , Also my second test tag did not apear in the remote. That confused me. I learned that there is the following switch and I tryed it. ``` git push --tag ``` That triggered git to push my local tags to the remote. Do you know if that is a gitea or gitea configuration specific behaviour? I did not observe such behaviour in github or gitlab yet. Cheers!
Author
Owner

Tags are not pushed automatically, this should be the same across all Git providers. (The flag should be --tags, by the way).

As far as I can see, it works now?

This PR seems obsolete as the branch has already been merged into main.

Tags are not pushed automatically, this should be the same across all Git providers. (The flag should be `--tags`, by the way). As far as I can see, it works now? This PR seems obsolete as the branch has already been merged into `main`.
dancingCycle closed this pull request 2022-12-13 17:02:36 +01:00
dancingCycle deleted branch test-drone 2022-12-13 17:02:53 +01:00
All checks were successful
continuous-integration/drone/pr Build is passing
continuous-integration/drone/push Build is passing

Pull request closed

Sign in to join this conversation.
No reviewers
No Milestone
No project
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: FreeFleetManagement/manual#3
No description provided.