WIP: implement basic ci pipeline #4

Draft
mightyBroccoli wants to merge 6 commits from droneci into master
Collaborator

resolves #3

resolves #3
mightyBroccoli added 3 commits 2021-07-26 16:35:35 +02:00
042914c968
ci: initial droneci configuration
+ add initial droneci configuration file
fa3af491d0
droneci: remove redundant info
- remove redundant plattform info
1ae8fe51ec
ci: pipeline configuration rebuild
* change pipeline configuration to be woodpecker compliant
* rename .drone.yml to .woodpecker.yml
mightyBroccoli added 1 commit 2021-07-26 17:59:24 +02:00
mightyBroccoli added 1 commit 2021-07-26 18:08:08 +02:00
continuous-integration/drone the build failed Details
abf72d1990
ci: start from scratch
genofire force-pushed droneci from 2a004097db to cc32509027 2021-09-16 01:10:58 +02:00 Compare
genofire force-pushed droneci from cc32509027 to e9ad6f0b1e 2021-09-16 01:38:48 +02:00 Compare
genofire force-pushed droneci from e9ad6f0b1e to 4d647ba3a3 2021-09-16 01:41:02 +02:00 Compare
genofire force-pushed droneci from 4d647ba3a3 to 09ce0f379a 2021-09-16 01:47:39 +02:00 Compare
genofire force-pushed droneci from 09ce0f379a to 431f72e6f0 2021-09-16 01:48:23 +02:00 Compare
genofire force-pushed droneci from 431f72e6f0 to 794100341c 2021-09-16 02:04:21 +02:00 Compare
genofire force-pushed droneci from 794100341c to 175ed0346d 2021-09-16 02:04:32 +02:00 Compare
Owner

oO - i believe it is my fault:

black . --check
would reformat cleanup.py
Oh no! 💥 💔 💥
1 file would be reformatted, 6 files would be left unchanged.

what should i do there?

oO - i believe it is my fault: ``` black . --check would reformat cleanup.py Oh no! 💥 💔 💥 1 file would be reformatted, 6 files would be left unchanged. ``` what should i do there?
Author
Collaborator

I am friend of clean pull requests, therefore I would plead for only ci changes and right after the pull request is merged we push the aforementioned changes.

Please correct me if I am wrong here, but I think this is way easier to understand what was done.

I am friend of clean pull requests, therefore I would plead for only ci changes and right after the pull request is merged we push the aforementioned changes. Please correct me if I am wrong here, but I think this is way easier to understand what was done.
Owner

I am totaly with you - it was just to mention, that the failure does not depends on the CI it-self (this PR).

I am totaly with you - it was just to mention, that the failure does not depends on the CI it-self (this PR).
Some checks failed
continuous-integration/drone the build failed
This pull request is marked as a work in progress.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b droneci master
git pull origin droneci

Step 2:

Merge the changes and update on Forgejo.
git checkout master
git merge --no-ff droneci
git push origin master
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
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: sum7/ejabberd-tools#4
No description provided.