Can anyone help me please as that branch is gone, I have Jenkins 2.73.3
installed but how do I use this feature as it says available from 2.30?
I've spent much longer on trying to get this to work than I thought I
would, for reference I've been over these before finally finding this forum
hmm, I checked out your branch:
https://github.com/stephenc/github-branch-source-plugin/tree/jenkins-34395
compiled and installed: 2.2.5-SNAPSHOT (private-e98acfa4-root)
but still not seeing any tags built
On Wednesday, 1 November 2017 16:54:22 UTC+1, Stephen Connolly wrote:
>
> 2.2.4 does not
ah, well that explains it :)
I should have paid more attention that the PR is still open
https://github.com/jenkinsci/github-branch-source-plugin/pull/158/
On Wednesday, 1 November 2017 16:54:22 UTC+1, Stephen Connolly wrote:
>
> 2.2.4 does not have discovery of tags merged yet
>
> On 1
2.2.4 does not have discovery of tags merged yet
On 1 November 2017 at 08:15, wrote:
> I've got version 2.2.4 of GitHub Branch Source Plugin installed, and
> compiled, installed, and configured my organization folder to use
>
I've got version 2.2.4 of GitHub Branch Source Plugin installed, and
compiled, installed, and configured my organization folder to
use https://github.com/AngryBytes/jenkins-build-everything-strategy-plugin
which uses:
@Override
public boolean isAutomaticBuild(SCMSource source, SCMHead
On 6 September 2017 at 23:24, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
> On Thu 7 Sep 2017 at 07:22, Stephen Connolly com> wrote:
>
>> You are waiting on https://github.com/jenkinsci/github-branch-
>> source-plugin/pull/158 to be merged then.
>>
On Thu 7 Sep 2017 at 07:22, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> You are waiting on
> https://github.com/jenkinsci/github-branch-source-plugin/pull/158 to be
> merged then.
>
> You could build the plugin with the PR merged and do some testing to help
> give better
You are waiting on
https://github.com/jenkinsci/github-branch-source-plugin/pull/158 to be
merged then.
You could build the plugin with the PR merged and do some testing to help
give better confidence for releasing that PR
On Thu 7 Sep 2017 at 00:43, wrote:
> Oh, to
The current git plugin does not provide a convenient way to build something
that has been tagged if it has already been built. If you're willing to be
on the cutting edge, you could install a pull request build
Oh, to clarify, we're using the "github branch source" plugin and I have
already confirmed that github is correctly firing the webhook.
On Wednesday, September 6, 2017 at 4:38:05 PM UTC-7, aham...@anchorfree.com
wrote:
>
> One of the fundamental concepts in CI/CD is "build once". So... we build
On Friday, July 14, 2017 at 7:56:00 AM UTC-8, Samuel Henrique wrote:
>
> Hello,
>
> I'm trying to make jenkins trigger a build whenever a new tag is pushed to
> my git repo.
>
> I already made it to trigger builds when a tag pointing to a new commit is
> pushed, by setting:
>
> *refspec:*
Hello,
I'm trying to make jenkins trigger a build whenever a new tag is pushed to
my git repo.
I already made it to trigger builds when a tag pointing to a new commit is
pushed, by setting:
*refspec:* +refs/tags/*:refs/remotes/origin/tags/*
> *branch specifier:* **
The problem is that the
12 matches
Mail list logo