I'm sorry, but could you please elaborate? :)
What changes to which plug-in and an example implementation...
Right now instead of "checkout scm" in the checkout stage and "git clone"
in the stage where I need to do git tag/push, I do only the following in
the checkout stage:
sshagent (credentia
You will be wanting my changes that should make a beta early next week
Then you add the local branch trait and that does exactly what you want
HTH
On Sat 17 Jun 2017 at 07:18, Idan Adar wrote:
> Checkouts in Jenkins, AFAIK, are headless, meaning that I cannot do git
> operations on them.
> If
Checkouts in Jenkins, AFAIK, are headless, meaning that I cannot do git
operations on them.
If I want to do an operation, like git tag and then git push... I need to
first do git clone inside an sshagent block or similar.
For large repositories this can be a problem, as the process becomes
leng
Jenkins 2.39 to 2.63,...Currently running 2.39 jenkins on centos, plannin
to upgrade to 2.63, we use a lot of multiconfiguration jobs and few
pipeline jobs,
Has anybody followed the above upgrade path, has anyone seen any issues
after the upgrade in job configuration or cpu issues or any other issu
Hi all,
Apologies for notifying you a few days late (I've been flying over the
pacific) but last week we shipped Blue Ocean 1.1 with fast search for
pipelines and a bunch of other goodies. You can get the details over
at https://jenkins.io/blog/2017/06/13/blueocean-1-1/ Oh, and don't forget
to
I will give it a spin too.
Thanks
-Dan
On Friday, June 16, 2017 at 11:57:26 AM UTC-7, Kevin Burnett wrote:
>
> we'd be down to try that, yes. thanks for making these changes in a way
> that will benefit the product long-term!
>
> fingers are crossed that there's already a built-in way to preten
is it possible to do that without a plugin?
If not, any recommendations for a plugin?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr.
You probably want to test 2.46.2, then start a git bisect to identify the
commit that introduced this possibly.
Cheers
2017-06-16 19:21 GMT+02:00 Matt Rabe :
> Got an issue with Nodepool / Jenkins setup, we're trying to upgrade to
> 2.46.3 but Nodepool fails with a 405 on the GET (it needs to be
Got an issue with Nodepool / Jenkins setup, we're trying to upgrade to
2.46.3 but Nodepool fails with a 405 on the GET (it needs to be a POST)
request to add the Jenkins node. In 2.46.1 this GET request succeeds and
the node is added. I'm wondering what changed so I have something to point
to w
we'd be down to try that, yes. thanks for making these changes in a way
that will benefit the product long-term!
fingers are crossed that there's already a built-in way to pretend like
pull requests don't exist! you're already building the branches; why also
build the pull requests, eh? :)
tha
I'd like to be part of the beta test.
Mark Waite
On Fri, Jun 16, 2017 at 12:19 PM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Just a quick status update.
>
> In final stages of this work now. Bobby is being a superstar and reviewing
> my 13k LoC change on the Bitbucket branch so
Just a quick status update.
In final stages of this work now. Bobby is being a superstar and reviewing
my 13k LoC change on the Bitbucket branch source - brings lots of feature
parity with GitHub and adds the configuration ability of the pure Git
branch source
I am finalising the GitHub Branch So
Yes it is working as designed.
https://jenkins.io/doc/pipeline/steps/workflow-multibranch/#properties-set-job-properties
"Note that any existing properties of the job will be replaced with the
list given here."
It would be nice to be able to modify job properties rather than overwrite
everythin
I mean, for the checkout scm part above... not a separate "git clone
--depth 1 ..."
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...
Could someone please provide an example for shallow clone in a declarative
pipeline?
pipeline {
options {
ansiColor('xterm')
skipDefaultCheckout()
disableConcurrentBuilds()
}
stages {
steps {
checkout scm
...
}
}
}
--
I forgot about parameters option in a Jenkinsfile... thanks.
On Thursday, June 15, 2017 at 8:12:15 PM UTC+3, Stephen Connolly wrote:
>
>
> On Thu 15 Jun 2017 at 17:44, Idan Adar >
> wrote:
>
>> Well that's a deadlock... I need both those variables and the parameter
>> provided to me via parametr
i would have to agree, this is definitely an issue. I'm currently using
Amazon EFS as the storage backend for my Jenkins master, who doesn't have
any executors. The flyweight executors checking out repositories is
definitely a concern of mine. EFS will automatically scale so storage isn't
a hug
Hi,
Does anybody interested in contract to upgrade existing Jenkins plug-in?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@google
Hi, Dan , Thanks for the hint, and I did find the job recreatd by job DSL
didn't have the problem
Hi, Andrew, thanks for the good news! Do we just upgrade all the plugins
to get the fix?
Qiang
On Friday, June 16, 2017 at 9:08:33 AM UTC-5, Andrew Bayer wrote:
>
> Yup, that was entirely my b
Oh, and you don't need to nuke the job - the configs will get fixed
automatically on next run of the job, and if you're unable to kick a build
off (due to https://issues.jenkins-ci.org/browse/JENKINS-44809), you can
run the script at
https://issues.jenkins-ci.org/browse/JENKINS-44809?focusedComment
Yup, that was entirely my bad, but is now fixed. Sorry about that!
A.
On Fri, Jun 16, 2017 at 1:09 AM, Dan Tran wrote:
> we encounter similar issue with declarative pipeline upgrade
> https://groups.google.com/forum/#!topic/jenkinsci-users/lAyx4kof0wU
>
> For you case, you may need drop and re
i use this a lot. If all you want is to display this in the build column on
the job's dashboard page, put any string in the variable field, in the
format field put ${BUILD_NUMBER} look at the ? help for other variables,
then check the box
Use the formatted version number for build display name.
hi,
I would like to change the build Name. I try to use Version Number Plugin
or Set Build Name.
I want to change the name with
"BUILD_DATE_FORMATTED"
For example : #01-2017-05-15-hh-mm
Number + today date + time
I dont know what do I put in"Environnement Variable Name" and Version
Numb
Okay, I solved my issue by running a shell command using find and a regexp
and renaming it.
On Thursday, June 15, 2017 at 6:35:55 PM UTC+2, milan.ze...@gmail.com wrote:
>
> Hello everyone,
> I have successfully managed to make Jenkins pull source from Assembla,
> build it and run it on an Androi
24 matches
Mail list logo
