Thanks. It did eventually kick off, but it certainly wasn't immediate,
more like several hours.
On Thu, Mar 12, 2020 at 3:26 PM Robert Scholte wrote:
>
> It should happen immediately. If not, then you have some options:
> - Log in on Jenkins and call "Scan Multibranch Pipeline Now" (or dedicated
It should happen immediately. If not, then you have some options:
- Log in on Jenkins and call "Scan Multibranch Pipeline Now" (or dedicated
branch if it exists)
- Go to https://selfserve.apache.org/ and select "Synchronize Git Repositories"
Robert
On 12-3-2020 13:10:26, Elliotte Rusty Harold
On Thu, Mar 12, 2020 at 2:46 PM Robert Scholte wrote:
>
> This week I was very surprised to see commits from the user call "github" in
> Jenkins:
> https://builds.apache.org/job/maven-box/job/maven-shared-utils/job/master/changes
>
>
> IMO we shouldn't want these kind of commits.
> Based on the m
This week I was very surprised to see commits from the user call "github" in
Jenkins:
https://builds.apache.org/job/maven-box/job/maven-shared-utils/job/master/changes
IMO we shouldn't want these kind of commits.
Based on the most recent activities I had a chat with Sylwester en Elliotte.
The r
How does Jenkins decide whether/when to run tests on any particular
branch? I've pushed a number of commits to a branch this morning but
the last build it ran from that branch was about 11 hours ago.
--
Elliotte Rusty Harold
elh...@ibiblio.org
Hi,
We fixed 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12345698
Staging repository:
https://repository.apache.org/content/repositories/maven-1557/
direct link to artifacts:
https://repository.apache.org/content/repositories/maven-1557/org/apache/m
