*Just to clarify*:
The variable is required before using the content of the repository.
That's true for the normal use of the Git plugin and also documented
looking at the question icon (in both cases, normal and the pipeline
variant)
The text:
- *${ENV_VARIABLE}*
It is also possible to us
Thanks Stephen
On Tuesday, April 5, 2016 at 3:42:25 PM UTC+5:30, Stephen Connolly wrote:
>
> SSH is encrypted, but uses Blocking I/O (unless you use the CloudBees
> proprietary NIO SSH Slave connector) so scalability can be limited.
>
> JNLPAgentProtocol2 is unencrypted and uses Non-Blocking I/O,
For our C++-based library, we'd like to automatically run ABI compliance
checks (and also API compat checks) as we update stuff, so we can plan
rolling out binaries better.
abi-compliance-checker is a great tool for this, but I haven't come up
with a good way to automate it yet. We already build e
Is there any way to get the durations of individual parallel branches and
stages from the Jenkins REST API? Or any other way to help us identify the
slow parts of our pipeline?
https://issues.jenkins-ci.org/browse/JENKINS-33185 will help. But is there
anything available now, or that will allow
On 05.04.2016, at 16:54, Stuart Warren wrote:
> Today is the first time I've tried groovy though, so probably doing something
> silly.
> Are there any obvious improvements to the above?
You could alternatively just go with patching the JENKINS_HOME so Jenkins
considers it not an update:
$ ec
On Friday, 1 April 2016 01:20:37 UTC+1, R Tyler Croy wrote:
>
> (replies inline)
>
> On Thu, 31 Mar 2016, Richard Bywater wrote:
>
> > It sounds to me like there's a good use-case for being able to skip the
> > setup wizard even in "prod" mode? Is the jenkins.install.runSetupWizard
> > ignore
Hi,
yes, I can confirm that behaviour. Taking a closer look at the log shows
that any build wrappers that inject e.g. Environment vars are not running
at this early stage.
My guess is, that the assumption was that these wrappers are instantiated
in the Jenkinsfile, so that they are not yet kn
SSH is encrypted, but uses Blocking I/O (unless you use the CloudBees
proprietary NIO SSH Slave connector) so scalability can be limited.
JNLPAgentProtocol2 is unencrypted and uses Non-Blocking I/O, so you get
back-pressure when the server is under load, but good scalability.
JNLPAgentProtocol3 i
A pom of pom where you list the required plugins as
where the hpi is used can do the download for
you. Here is a snippet showing what you need to do (this is also used in
creating the Jenkins 1.x WAR files and if it isn't then it should have been
org.jenkins-ci.plugins
metrics
3.1.2.5
hpi
provi
Hi Geoffroy,
Thanks for reply back and providing useful information.
On 4 April 2016 at 22:32, wrote:
> Hello
>
> by itself the plugin is not enought to configure resilient builds. If the
> jenkins masters crashes during the build, then build will be lost even if
> jenkins mesos plugin would be
Thanks for the reply jpd4nt.
for anybody - any other advantages between these two protocols.
Thank,
Naveen
On Monday, April 4, 2016 at 10:43:18 PM UTC+5:30, jpd4nt wrote:
>
> Hi Naveen.
>
> I find ssh option more robust because our Jenkins master is behind a load
> balancer so the web start has
You can easily query those details via the Rest API:
- https://YOUR_JENKINS_URL/job/YOUR_JOB_NAME/api
Cheers
On Monday, 4 April 2016 23:05:01 UTC+1, Dani Chelios wrote:
>
> Any news about this?
>
> On Tuesday, June 2, 2015 at 5:55:35 PM UTC-5, Pravin Patil wrote:
>>
>> I have RTCv5.0.2 integrate
Hi,
Mode: Pipeline script from SCM
I tried to change working example to take a TAG as String parameter
and to use *${TAG}* for the Branch using the Pipeline job in Jenkins 2.x
When trying this I get this:
> git rev-parse origin/${TAG}^{commit} # timeout=10
> git rev-parse ${TAG}^{commit} # ti
13 matches
Mail list logo
