Re: Fastest way to git tag in a Jenkinsfile?

[Idan Adar]

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 (credentials: ['...']) {
sh "git clone --depth 1 -b develop g...@myrepo.git"
}

And then I should be able to do the operations...
Essentially, Jenkinsfile now does the "checkout" not-headlessly, but it 
does meant it's not declarative anymore...

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b1020fe2-961e-4586-8b19-0f6c51879cad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fastest way to git tag in a Jenkinsfile?

[Stephen Connolly]

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 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
> lengthy...
> checkout scm...
> do stuff (tests, build, etc)...
> git clone...
> git tag...
> git push...
>
> This can be made a little better by git cloning using --depth 1, but this
> still will git clone the whole repo, even if without history.
>
> So I'm looking for a way to be able to git tag/push, but not also git
> clone the repo again... is this at all possible, to maybe check scm with
> head (or, not headless) so git operations would be possible?
>
> --
> 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...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/52f875bc-020c-422f-8508-2277a628f608%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Sent from my phone

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMw1YnzxswbOZKM%2BfJa2nqD9j5OZ0A%3DD%2B3_mNiiemepEew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Fastest way to git tag in a Jenkinsfile?

[Idan Adar]

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 
lengthy...
checkout scm...
do stuff (tests, build, etc)...
git clone...
git tag...
git push...

This can be made a little better by git cloning using --depth 1, but this 
still will git clone the whole repo, even if without history.

So I'm looking for a way to be able to git tag/push, but not also git clone 
the repo again... is this at all possible, to maybe check scm with head 
(or, not headless) so git operations would be possible?

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/52f875bc-020c-422f-8508-2277a628f608%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins 2.39 to 2.63

[Kishore RP]

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 issues...
Which can help to decide whether to upgrade or not...
Thanks in advance for the help

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAH%3D%3DDrpu24Y-06rq68crPcLCAcD-6RS-d7YpMAaq62EcPspESA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Blue Ocean 1.1 has been released with fast search and more

[James Dumay]

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 tweet or share the blog post to help get the word out! 

I'd like to thank our users and contributors for all the bug reports and 
patches that they have sent through since 1.0. Without your help we 
wouldn't have been able to fix over 48 bug fixes in this release.

We are focusing next on Github Enterprise, Bitbucket Cloud/Server and 
native Git support for the Pipeline Editor. There is also some great 
improvements coming by way of Declarative Pipeline that we will start 
surfacing in the editor, such as Parallel Stages 

.

Thanks for your support and enjoy the new release :)

Cheers,
James


-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/51ea06a0-b9f9-4ac6-98cb-751e78f41578%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GitHub and Bitbucket branch source UI refactoring

[Dan Tran]

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 pretend like 
> pull requests don't exist! you're already building the branches; why also 
> build the pull requests, eh? :)
>
> thanks!
> kb
>
>
> On Friday, June 16, 2017 at 2:35:54 PM UTC-4, Mark Waite wrote:
>>
>> I'd like to be part of the beta test.
>>
>> Mark Waite
>>
>> On Fri, Jun 16, 2017 at 12:19 PM Stephen Connolly <
>> stephen.al...@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 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 Source changes... likely to be another 
>>> big PR
>>>
>>> Then there's a 5k LoC change in the Git plugin
>>>
>>> Plan is to try and get all merged next week and cut a beta
>>>
>>> I'll be looking for people to help test at that stage.
>>>
>>> Please respond if you think you can help (lots of bugs fixed as a side 
>>> effect of the refactoring - it makes things more easy to test => I found 
>>> and fixed bugs)
>>> -- 
>>> Sent from my phone
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxfYrZphgYDXFD3i%2Bo_7eDn7mn2qVrzJz6wFaoVkNmc%2Bw%40mail.gmail.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5dd15ac2-b8a2-4ebd-bb4a-3bffa4815227%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

distributing binaries & files with Jenkins jobs

[TI]

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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e476f5fe-398e-4b18-b3ac-5c0ea3d83dfd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 405 error from doCreateItem on 2.46.3, not on 2.46.1

[Baptiste Mathus]

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 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 with Nodepool if a fix needs to go in there.
>
> --
> 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...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/e6f46619-e8cf-4529-b37d-12047082c81c%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7N9ktj9_6_AbLVetS5LOrDG%2Bj_j1RU80iRWjXu-%3D%3D2OA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

405 error from doCreateItem on 2.46.3, not on 2.46.1

[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 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 with Nodepool if a fix needs to go in there.

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e6f46619-e8cf-4529-b37d-12047082c81c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GitHub and Bitbucket branch source UI refactoring

[Kevin Burnett]

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? :)

thanks!
kb


On Friday, June 16, 2017 at 2:35:54 PM UTC-4, Mark Waite wrote:
>
> I'd like to be part of the beta test.
>
> Mark Waite
>
> On Fri, Jun 16, 2017 at 12:19 PM Stephen Connolly  > 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 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 Source changes... likely to be another 
>> big PR
>>
>> Then there's a 5k LoC change in the Git plugin
>>
>> Plan is to try and get all merged next week and cut a beta
>>
>> I'll be looking for people to help test at that stage.
>>
>> Please respond if you think you can help (lots of bugs fixed as a side 
>> effect of the refactoring - it makes things more easy to test => I found 
>> and fixed bugs)
>> -- 
>> Sent from my phone
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxfYrZphgYDXFD3i%2Bo_7eDn7mn2qVrzJz6wFaoVkNmc%2Bw%40mail.gmail.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fd613b68-3f87-4650-a3f9-6657d8f4179a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GitHub and Bitbucket branch source UI refactoring

[Mark Waite]

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 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 Source changes... likely to be another
> big PR
>
> Then there's a 5k LoC change in the Git plugin
>
> Plan is to try and get all merged next week and cut a beta
>
> I'll be looking for people to help test at that stage.
>
> Please respond if you think you can help (lots of bugs fixed as a side
> effect of the refactoring - it makes things more easy to test => I found
> and fixed bugs)
> --
> Sent from my phone
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxfYrZphgYDXFD3i%2Bo_7eDn7mn2qVrzJz6wFaoVkNmc%2Bw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGSd51psLxAV%2BVV0YkxR8gY5Tc58LuzWPWnasUGP-cAYg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

GitHub and Bitbucket branch source UI refactoring

[Stephen Connolly]

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 Source changes... likely to be another
big PR

Then there's a 5k LoC change in the Git plugin

Plan is to try and get all merged next week and cut a beta

I'll be looking for people to help test at that stage.

Please respond if you think you can help (lots of bugs fixed as a side
effect of the refactoring - it makes things more easy to test => I found
and fixed bugs)
-- 
Sent from my phone

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMxfYrZphgYDXFD3i%2Bo_7eDn7mn2qVrzJz6wFaoVkNmc%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Job properties are not (should be !?) cumulative

[harold . putman]

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 
everything. It makes for a confusing user experience when you set job 
properties manually, and then have them blown away when your pipeline job 
runs. 

I've been working around it by first reading the properties I want to 
preserve and then writing them back, but this is ugly and very undocumented.


On Friday, May 19, 2017 at 4:28:12 AM UTC-4, nco...@lbisa.com wrote:
>
> Project properties are not cumulative when additional settings are set 
> during the pipeline.
>
>
> For example, if setting a Parameterized build and later in the pipeline, 
> a Discard Old Builds is set, the Parameterized build is unset.
>
> I had this happening when the Discard Old Builds were used in a Shared 
> library, later in the pipeline.
>
>
> When a additional propertie is set, it shouldn't unset all the previous 
> properties, if they are not the same type (discard builds vs parameters).
>
>
> Someone know if this is working as designed or is something that could be 
> implemented?
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/167f7cb9-64fd-4f85-b473-0cde1f7613e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Shallow clone example for declarative pipeline?

[Idan Adar]

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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/616a459f-55d4-4511-b061-b0188fbe6b54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Shallow clone example for declarative pipeline?

[Idan Adar]

Could someone please provide an example for shallow clone in a declarative 
pipeline?

pipeline {
   options {
  ansiColor('xterm')
  skipDefaultCheckout()
  disableConcurrentBuilds()
   }
   
   stages {
 steps {
 checkout scm
 ...
 }
   }
}

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b2ab1afe-1ea9-46f1-81c9-4509a4d56c8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can a Jenkins global variable be used inside running code as part of a job?

[Idan Adar]

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 parametrized build...
>> parametrized build is available in pipeline but not multibranch
>>
>
> If can define the parameters from your Jenkinsfile
>
> An alternative is to use a different Jenkinsfile (in a different repo) for 
> the deployment 
>
>>
>>
>> -- 
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/67314e16-6ae2-4c93-84ed-b76b5d46f0de%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Sent from my phone
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/711fed79-4222-47a5-8014-58c62cd39576%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Run pipeline flyweight executors off of master

[Joshua Noble]

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 huge issue for me, but duplication and clone times are. (for larger repos)

On Wednesday, August 10, 2016 at 2:31:45 PM UTC-4, Kevin Phillips wrote:
>
> In my opinion, even more problematic than possibly running unsafe code in 
> a flyweight executor on the master is the fact that these flyweight 
> pipeline threads perform a full checkout of the target repository - at 
> least when using Git as the SCM. So if one has a relatively large code 
> repository containing product code - say several gigabytes - and they want 
> to store their Jenkinsfile with the code so they can leverage the 
> MultiBranch options in Jenkins Pipeline, they end up with many copies of 
> their entire codebase being checked out on the master, possibly causing the 
> master to run out of disk space. Add to this the fact that these 
> "temporary" workspaces created on the master by the flyweight tasks are not 
> automatically deleted when not in use and there is no way to purge them 
> from the Jenkins dashboard and you are just asking for problems. This isn't 
> a case of whether this will become a problem as much as it is an issue of 
> when it will become a problem.
>
> In my opinion, Jenkinsfile's stored in SCM should be checked out on an 
> agent as a typical freestyle job would do, and a default "node" allocated 
> by the executor that launches the script contained therein for the node on 
> which it is already running on. Then the rest of the Jenkinsfile could be 
> processed in place without requiring any sort of flyweight executor at all, 
> and avoiding the issues with having multiple checkouts of the same code 
> spread across a build farm. Also, I think this would be inline with how 
> some other more modern continuous integration servers work like travis-ci, 
> so it's not without precidence.
>
> On Monday, June 13, 2016 at 6:03:20 PM UTC-3, Eli White wrote:
>>
>> We follow the Jenkins configuration best practices and have no executors 
>> on our master node and force everything to run on our agents. 
>>
>> We are starting to work with pipeline jobs and are worried that bad 
>> Jenkinsfiles could cause problems on our master. 
>> How can we force the flyweight jobs to run on a designated machine 
>> *other* than master? 
>>
>> How do other people handle this?
>>
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d6b297d9-0a17-42ea-a608-45f324b33caf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Anybody interested in contract?

[Evgueni Kolossov]

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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b609c5ae-c9da-4f3e-ab58-144ea593fa02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Growing config.xml with GitLab plugin

[Qiang]

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 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 recreate the job
>>
>> -Dan
>>
>> On Thursday, June 15, 2017 at 9:15:11 PM UTC-7, Qiang wrote:
>>>
>>> Recently I upgraded to Jenkins 2.46.3 (based on the docker image 
>>> release). There is a "new weird" problem. I noticed job's config.xml grow 
>>> really big. When open it , it has tons of repeated following code
>>>
>>>
>>> >> reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
>>> >> reference="../jenkins.model.BuildDiscarderProperty"/>
>>> >> reference="../com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty"/>
>>> >> reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
>>> >> reference="../jenkins.model.BuildDiscarderProperty"/>
>>> >> reference="../com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty"/>
>>> >> reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
>>> >> reference="../jenkins.model.BuildDiscarderProperty"/>
>>> >> reference="../com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty"/>
>>> >> reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
>>> >> reference="../jenkins.model.BuildDiscarderProperty"/>
>>>
>>> This was not observed before the upgrade (Jenkins ver. 2.46.2 
>>> )
>>> Even though I upgraded plugin versions, the GitLab plugin stays the same 
>>> (1.4.5)
>>>
>>>
>>> Wonder if any one else have seen this, and do you have any workaround or 
>>> fix? 
>>>
>>> Thanks!
>>> Qiang
>>>
>>> -- 
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/051604eb-0fec-46ce-98eb-272a3a36c8e2%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/839e7ca5-1592-4003-a078-e273939c5180%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Growing config.xml with GitLab plugin

[Andrew Bayer]

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?focusedCommentId=302837&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-302837
in the Jenkins Script Console to manually clean up the bogus properties.

A.

On Fri, Jun 16, 2017 at 10:07 AM, Andrew Bayer 
wrote:

> 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 recreate the job
>>
>> -Dan
>>
>> On Thursday, June 15, 2017 at 9:15:11 PM UTC-7, Qiang wrote:
>>>
>>> Recently I upgraded to Jenkins 2.46.3 (based on the docker image
>>> release). There is a "new weird" problem. I noticed job's config.xml grow
>>> really big. When open it , it has tons of repeated following code
>>>
>>>
>>> >> reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
>>> >> reference="../jenkins.model.BuildDiscarderProperty"/>
>>> >> reference="../com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty"/>
>>> >> reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
>>> >> reference="../jenkins.model.BuildDiscarderProperty"/>
>>> >> reference="../com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty"/>
>>> >> reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
>>> >> reference="../jenkins.model.BuildDiscarderProperty"/>
>>> >> reference="../com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty"/>
>>> >> reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
>>> >> reference="../jenkins.model.BuildDiscarderProperty"/>
>>>
>>> This was not observed before the upgrade (Jenkins ver. 2.46.2 
>>> )
>>> Even though I upgraded plugin versions, the GitLab plugin stays the same 
>>> (1.4.5)
>>>
>>>
>>> Wonder if any one else have seen this, and do you have any workaround or 
>>> fix?
>>>
>>> Thanks!
>>> Qiang
>>>
>>> --
>> 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...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-users/051604eb-0fec-46ce-98eb-272a3a36c8e2%
>> 40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPbPdOaeuHN2to4RQ2PH_rtrWPDKEuaNMVPjR-_QXMsBF%3Degrw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Growing config.xml with GitLab plugin

[Andrew Bayer]

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 recreate the job
>
> -Dan
>
> On Thursday, June 15, 2017 at 9:15:11 PM UTC-7, Qiang wrote:
>>
>> Recently I upgraded to Jenkins 2.46.3 (based on the docker image
>> release). There is a "new weird" problem. I noticed job's config.xml grow
>> really big. When open it , it has tons of repeated following code
>>
>>
>> > reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
>> > reference="../jenkins.model.BuildDiscarderProperty"/>
>> > reference="../com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty"/>
>> > reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
>> > reference="../jenkins.model.BuildDiscarderProperty"/>
>> > reference="../com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty"/>
>> > reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
>> > reference="../jenkins.model.BuildDiscarderProperty"/>
>> > reference="../com.dabsquared.gitlabjenkins.connection.GitLabConnectionProperty"/>
>> > reference="../hudson.plugins.buildblocker.BuildBlockerProperty"/>
>> > reference="../jenkins.model.BuildDiscarderProperty"/>
>>
>> This was not observed before the upgrade (Jenkins ver. 2.46.2 
>> )
>> Even though I upgraded plugin versions, the GitLab plugin stays the same 
>> (1.4.5)
>>
>>
>> Wonder if any one else have seen this, and do you have any workaround or fix?
>>
>> Thanks!
>> Qiang
>>
>> --
> 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...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/051604eb-0fec-46ce-98eb-272a3a36c8e2%40googlegroups.
> com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPbPdOaRf4CGatP2nKK3m06zA3bgzbo8VOseAZQKWX2SWt6%3DCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How do you use the Version Number Plugin to modify the Build Name ?

[Richard Ginga]

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.



On Fri, Jun 16, 2017 at 5:54 AM, Philippe Maire  wrote:

> 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
> Number.." field ?
>
> and to use Build Name?
>
> Thank you to help me
> Phil
>
>
>
>
>
>
> 
>
>
> 
>
> --
> 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...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/7a14f69c-1142-469b-a8ae-863f194bcb79%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAL3PpaVGLhWpLq8E670zrmamZz%2BS010YcbHno6bH4nywkA0xpw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

How do you use the Version Number Plugin to modify the Build Name ?

[Philippe Maire]

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 
Number.." field ?

and to use Build Name?

Thank you to help me
Phil









-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7a14f69c-1142-469b-a8ae-863f194bcb79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Get path to generated APKs

[milan . zelenka1991]

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 Android simulator by specifying the path to the 
> generated APK in "Install Android package" build step. 
>
> What I need now is not to have to hardcode this path because the name of 
> the generated APK file changes with the program's version and it would need 
> to be changed every time the program's version is changed. Is any there a 
> way to do that? 
>
> Thank you for your help.
>

-- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/abb85ed6-216e-425c-a8d5-dbf5e7fcb46c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.