Woodpecker CI workflows (PR and develop releases) #3477
No reviewers
Labels
No labels
BE Request
Backlog
Better behavior
Blocked by deps
Bug
Code Review
Discussion
Doing
Feature Request / Enhancement
In the shining bright future maybe
It's complicated
MS Edge
Mememoon (or other niche browsers)
Missing API
Missing feature
Missing l10n/i18n
NL1
NL2
NL4
Need to verify on develop
RELEASE BLOCKER
Reassign or Close
Refactor
Regression
Safari
To Do
User story
Waiting on godot
accessibility
better documentation
chore
confirmed
easy ticket
incident
l10n update
mastoapi
mobile
needs design
needs-info
needs-review
stupid
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Depends on
#7872 Woodpecker CI develop/stable releases
pleroma/pleroma
Reference
pleroma/pleroma-fe!3477
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "phnt/pleroma-fe:woodpecker-pr-ci"
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?
pr-<pr number>as the versionpr-<pr number>as the version<default branch<-<8 char commit sha>as the version<default branch<-<8 char commit sha>as the versionTODO
Also I guess before this gets merged, agents should be tagged accordingly for the himem test workflow so I can add it as a label here. Filtering by platform is done automatically I think, after
is added to the workflow.
How does one deploy a runner for woodpecker ci?
Install docker, download docker image, mount the host Docker socket to the container and that's it.
Platform restrictions are handled by default.
There are two ways you can register it.
Runner tagging and the secret are handled via an env variable to the container.
Here's how I ran one locally when testing this:
Additionally enabling WOODPECKER_GRPC_SECURE=true is also probably a good idea.
https://woodpecker-ci.org/docs/administration/configuration/agent
are you sure 9000 port exposed?
i'm getting
transport: Error while dialing: dial tcp 178.156.170.121:9000: connect: connection refusedusing docker-compose
I haven't done this on Pleroma's own Woodpecker instance, I did it on my own Gitea instance.
Your config should work once that port is opened. cc @lambadalambda
PR Woodpecker CI workflowto WIP: PR Woodpecker CI workflowWIP: PR Woodpecker CI workflowto PR Woodpecker CI workflowPR Woodpecker CI workflowto WIP: PR Woodpecker CI workflowMarked as WIP and dependent on BE PR since E2E test needs the Docker images from there.
419b00dcaato01bd39b785WIP: PR Woodpecker CI workflowto WIP: Woodpecker CI workflows (PR and develop releases)01bd39b785tof346a17756f346a17756to2326d559b0WIP: Woodpecker CI workflows (PR and develop releases)to Woodpecker CI workflows (PR and develop releases)