The build on ci-builds is rather useless now. If I try to start a build on the one of the branches, I get: 14:35:37 Jenkins-Imposed API Limiter: Current quota for Github API usage has 1529 remaining (810 over budget). Next quota of 5000 in 33 min. Sleeping for 13 min. 14:35:37 Jenkins is attempting to evenly distribute GitHub API requests. To configure a different rate limiting strategy, such as having Jenkins restrict GitHub API requests only when near or above the GitHub rate limit, go to "GitHub API usage" under "Configure System" in the Jenkins settings." I have no clue what the github actions and github api are needed for. Whats the usecase for all this setup?
ci-build also has now jobs for all branches, which we don't need. I changed the configuration to 'master|archiva-2.x' in archiva-projects. Not sure, if this is the right place for this. Do you have built and released the archiva-redback-core release 2.6.2 already? Regards Martin Am Sonntag, 17. April 2022, 02:15:44 CEST schrieb Olivier Lamy: > On Sun, 17 Apr 2022 at 04:15, Martin <[email protected]> wrote: > > > Hi Olivier, > > > > I saw that you have added github actions and changed some build settings > > for archiva 2.x branch. > > > > Uhm I need to fix this to publish archiva-2.x branch snapshot. > because snapshots were deployed when pushing to a branch or a PR which was > wrong as we want to deploy from master or archiva-2.x only when branch or > PR are merged. > I should have fixed it now. > I had to remove the legacy project type gitbox as it's not supported > anymore and move to Github organisation. > > There is still something I don;t understand why IT tests are not > executed in the main build/jenkinsfile and move to another job. This cause > issues when working in a branch or a PR. > Why not have everything in the same build? > > > > The current snapshot artifacts are currently not published to our archiva > > repository https://archiva-repository.apache.org > > during the build process. > > > > Was this intended? > > > > Is there another place where the artifacts can be downloaded (github)? > > > > if not, I'm not sure what commit changed this behaviour, maybe you can > > give a hint. > > > > Thx > > > > Martin > > >
signature.asc
Description: This is a digitally signed message part.
