Build with Drone #3

Brain · 2022-11-22T13:58:33+01:00

Brain commented

2022-11-22 13:58:33 +01:00

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

continuous-integration/drone/pr Build is passing Details

continuous-integration/drone/push Build is passing Details

72d0012f33

Separate pipelines for PRs and releases

Brain changed title from ~~WIP: Build with Drone~~ to Build with Drone

2022-11-22 14:07:34 +01:00

Brain commented

2022-11-22 14:09:42 +01:00

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

dancingCycle commented

2022-11-22 15:26:38 +01:00

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!

dancingCycle commented

2022-12-02 12:12:50 +01:00

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

dancingCycle referenced this pull request

2022-12-02 12:17:38 +01:00

Add Drone Plugin gitea_release #2

dancingCycle commented

2022-12-08 22:24:01 +01:00

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.

dancingCycle commented

2022-12-13 12:33:49 +01:00

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!

Brain commented

2022-12-13 16:03:25 +01:00

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

continuous-integration/drone/pr Build is passing

Details

continuous-integration/drone/push Build is passing

Details