Build with Drone #3
No reviewers
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: FreeFleetManagement/manual#3
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "test-drone"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
is necessary to only run on a push event on
main
or a PR towardsmain
. 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 themake bundle
command, so it doesn't need to be installed at the moment.WIP: Build with Droneto Build with DroneThis 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.Hi @Brain,
The
main
branch builds on my host. Thetest
tag is also there now.Is the next step to create a secret in drone?
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!
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.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.
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!
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
.Pull request closed