Looking at the timestamps and the logs, most but not all of these
'workflow-fallback' directories get created after reapplying Configuration
as Code not after a restart and it doesn't look like the builds are being
interrupted. Though for some reason there's a large delay between the
original
I have 1 code repo that should be triggering jobs, and a separate repo for
a jenkins pipeline library. There are 2 jenkins jobs that use the ‘GitHub
hook trigger for GITScm polling’ build trigger, both are pipeline jobs
using the ‘Pipeline script from SCM’ with the repository configured to
ar" command `git` with the `checkout` command. Pipeline Syntax link on
> the Pipeline pages will help get the correct syntax for the details of the
> checkout command.
>
> On Thu, May 16, 2019 at 7:25 AM James Robson
> wrote:
>
>>
>>
>> On Wed
On Wednesday, 15 May 2019 21:28:52 UTC+1, Mark Waite wrote:
>
>
> You can often avoid the guessing by naming the branch precisely, as in
> 'origin/develop'.
>
I attempted to use 'origin/develop' as the branch name, but that causes the
job to fail the checkout with "ERROR: Couldn't find any
I have a repo with a branch called ‘develop’ and another branch called
‘kassandra/develop’. I have created a pipeline job that is building on
‘develop’, set to trigger with the ‘GitHub hook trigger for GITScm
polling’.
I expect this job to run only when ‘develop’ is changed, however it is
