A lot of people is close the pr. Then wait like 30 seconds. And reopen it.
On Fri., Oct. 4, 2019, 6:56 p.m. Mark Waite,
wrote:
> The simplest technique for me has been to use `git commit --amend` on the
> most recent commit, then force push that change to the repository. There
> is almost
The simplest technique for me has been to use `git commit --amend` on the
most recent commit, then force push that change to the repository. There
is almost always something that I can improve about the last commit in a
pull request.
On Fri, Oct 4, 2019 at 7:45 PM Richard Bywater wrote:
> Hi
>
Hi
One of my pull requests failed on ci.jenkins.io due to what looks like an
infrastructure issue (
https://ci.jenkins.io/job/Plugins/job/htmlpublisher-plugin/view/change-requests/job/PR-48/3/console
)
Is there a way of getting it to re-run the build job on the PR as I don't
seem to have access
I do understand the value for using other CI/CD systems. My only concerns
are when there are different GitHub checks and some of them are green and
some others are red. That particular lack of reliability might imply more
steps to troubleshoot to debug logs in different systems. I like the idea
I prefer the freedom, why restrict as long as it benefits the project and
does not create any hindrance?
The reason for configuration-as-code to have both GitHub actions, Travis
and ci.jenkins.io because we have experienced issues with both
ci.jenkins.io and travis, so useful to being able to
I've seen some repos already using GitHub actions, Travis and some others
tools, which from a collaborator point of view doesn't look easy to follow
up what GitHub checks are valuable.
I'd prefer to avoid using GitHub actions as much as possible for the
benefit of a more stable ci.jenkins.io
Hello,
I made a pull request to improve support for pipeline to the repo plugin,
to support passing environment variable, but I still got no feedback. The
patch is here: https://github.com/jenkinsci/repo-plugin/pull/54
Can anybody give some feedback?
Best regards,
--
You received this message
Hello,
Infrastructure for windows seems to be broken. Could you have a look
please? Getting the below messages in build log:
[2019-10-04T11:05:00.301Z] Still waiting to schedule task
[2019-10-04T11:05:00.301Z] Waiting for next available executor on ‘linux’
[2019-10-04T11:07:05.627Z]
So right now Olbak the ACI agents are failing creating large queue.
ci.jenkins.io must be stable if you want us to continue using it.
On Thursday, October 3, 2019 at 12:18:34 PM UTC+2, Olblak wrote:
>
> While I understand the value of Github Actions, I would not enable it on
> jenkins-infra
