On 08.06.2017 14:55, Derrik Ammons wrote:
> But, Jenkins thinks the build is located in the last incremented build
> directory. For example, if the previous build was 5.0.5 (24), and the
> source code has 5.1.0, the iOS app has 5.1.0.1 but it's the link to
> the build artifacts points to build 25
Thanks for the suggestion.
I made the changes (see repository
https://github.com/SimonMatthews-BP/BPWarnings), but I still get the same
error.
The repository version uses
src/main/java/hudson/plugins/warnings/parser/RunBluePearlParser.java and
(replies inline)
On Thu, 08 Jun 2017, Marley Kudiabor wrote:
> I'm wondering if I'm doing something wrong the syntax seems radically
> different between Declarative Pipelines and just placing everything inside
> a "node" block.
>
> I was wondering what format I should use to place pipeline
I am unable to change the applications that will be run, so there is no way
for me to add limitations to them, nor will the people who can modify them
do so for me, unfortunately. Thank you for the suggestion, though, I had
not considered adding a limitation to end the application
You don’t specify why you don’t want to create extra job parameters, but if it
is to prevent users that run the downstream job from setting it when firing off
the build, then I would suggest using a combination of the Hidden Parameters
plugin and the Parameterized Build Trigger plugin.
The
Richard, thank you! This is exactly what I was looking for!
On Thursday, June 8, 2017 at 1:37:49 PM UTC-7, Richard Ginga wrote:
>
> I think there is a BUILD_CAUSE token that every freestyle job gets when it
> runs.
>
> Check the Environ Injector Plugin for more details
>
> On Thu, Jun 8, 2017
I'm wondering if I'm doing something wrong the syntax seems radically
different between Declarative Pipelines and just placing everything inside
a "node" block.
I was wondering what format I should use to place pipeline steps inside of
Declarative Pipelines
For example
node {
stage
I think there is a BUILD_CAUSE token that every freestyle job gets when it
runs.
Check the Environ Injector Plugin for more details
On Thu, Jun 8, 2017 at 4:28 PM, Victoria Kozel
wrote:
> Hello,
>
> I am trying to pass environment variables from Upstream Job to a
>
Hello,
I am trying to pass environment variables from Upstream Job to a Downstream
Job without writing properties file to disk or creating extra job
parameters. Basically, my Downstream job needs to know if it was triggered
by upstream or not.
Thanks!!
--
You received this message because
As far as I can tell, it's not actually the plugin that's the problem.
Rather, Jenkins only asks the "cloud" provider (in this case, ECS) to
create a new node when there are zero nodes available. Thus, as long as
there is one job running, Jenkins sees it as a valid node and will politely
You may want to take a look at Job Object and cook this limitation right
inside the application you run into the batch script
https://msdn.microsoft.com/en-us/library/windows/desktop/ms684161(v=vs.85).aspx
example C++
#include
#define BYTES_PER_GIGABYTE ((size_t)1073741824);
...
Yeah, you can use something like
stages {
stage("foo") {
steps {
dir("some-dir") {
checkout ...
}
}
}
On Thu, Jun 8, 2017 at 12:02 PM, Mark Waite
wrote:
> The scripted pipeline has a dir() and a ws() command which can be used as
> a
(replies inline)
On Thu, 08 Jun 2017, Changqin Xie wrote:
> Using the following Jenkinsfile:
> #!/usr/bin/env groovy
>
> pipeline {
> agent any
>
> stages {
> stage('Deploy') {
> steps {
> sh 'echo $HOME'
> }
> }
> }
> }
>
>
Using the following Jenkinsfile:
#!/usr/bin/env groovy
pipeline {
agent any
stages {
stage('Deploy') {
steps {
sh 'echo $HOME'
}
}
}
}
And I get $HOME == /var/www
Why isn't it being "/home/www-data"? By the way, I am running
Hi,
when using the official docker image for Jenkins LTS (2.46.3) and also
using the build in mechanism, to install plugins (and it's dependencies)
via install-plugins.sh
then some of these plugins won't run with LTS, as they require a newer
version of jenkins.
f.e.
Pipeline: Job v2.12 -
The scripted pipeline has a dir() and a ws() command which can be used as a
wrapper around a checkout. I haven't looked to see if the same is
available in declarative.
I'd prefer that the git plugin "checkout to subdirectory" not be used in
pipeline, since there is already a concept for creating
steps 'git' and 'svn' are actually shortcuts for checkout step with
corresponding $class.
The problem is, that $class: 'GitSCM' does not accept parameter local: ,
so it checks everything out to the workspace root anyway, promptly
wiping out results of previous step... Looks like there is
I have a Jenkins pipeline like:
node("slave1"){
echo "Building very very complicated things"
}
If the node "slave1" does not exist in my Jenkins setup, the build is stuck
forever.
I know I could use timeout keyword and wrap the node command. However, this
is not good since timeout can happen
Hello,
I am trying to find a way to view the physical memory usage of a command
line application started by a build step in a Jenkins job on a Windows
operating system while it is running.
I tried using the Monitoring and Disk Usage plug-ins, however, the closest
I was able to do was
Is there any plugin that you recommend for implementing the lockout of the
login view for a certain IP, after a certain amount of failed login
attempts?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop
I actually have bot the Version Number Plugin and Next Build Number Plugin
and used them both before in jobs before Pipelines came around.
Now that I have a Jenkinsfile for the Mutibranch Pipeline, I am not sure how
to set the Version at build time for Jenkins. I retrieve the Release Number
from
>From unknown reason files under /var/lib/jenkins were removed from my
Jenkins master machine.
It reproduced three times.
To enable Jenkins to work I had to restore jenkins jobs.
The error I see in system log -
Caused: java.util.MissingResourceException: Unable to load resource
That's not matching the package layout of your code:
The resources for your class need to be in the same package layout, since
you have your code in:
src/main/java/hudson/plugins/bluepearl
Your resource would need to be in
src/main/resources/hudson/plugins/bluepearl
On Wed, Jun 7, 2017 at
I got super-confused here for a minute, so I thought it might be worth
pointing out that people who are using multibranch pipelines can completely
ignore the article presented in this thread (it says it's for
"non-multibranch jobs") and get this bitbucket server add-on
instead:
I forgot to add a time:
8:00 AM PDT/ 4 PM UTC
On Thu, Jun 8, 2017 at 6:21 AM, Patrick Wolf wrote:
> Join us today for our monthly Demo Day to show off the latest features we
> have been working on in Jenkins. This month we will show changes in
> Pipeline, Remoting, and
Join us today for our monthly Demo Day to show off the latest features we
have been working on in Jenkins. This month we will show changes in
Pipeline, Remoting, and LDAP.
https://www.youtube.com/watch?v=XRIiY0ZFn2c
--
You received this message because you are subscribed to the Google Groups
Hi,
My pipeline script sometimes fails on the error above.
the pipeline runs a few FreeStyleBuilds using parallel step, some of them
sometimes throw this exception, but sometimes succeed.
I tried to find the root cause, but the stacktrace is too general. I also
read the Serialization tutorial and
On 08.06.2017 14:02, Richard Ginga wrote:
> The Next Build Number only lets you increment the build number. you
> can't set it back to anything because the build number is a very
> integral part of how Jenkins works.
But the Version Number Plugin
The Next Build Number only lets you increment the build number. you can't
set it back to anything because the build number is a very integral part of
how Jenkins works.
On Wed, Jun 7, 2017 at 7:30 PM, Daniel Becroft wrote:
> Would the Next Build Number plugin provide any
On Wed, 7 Jun 2017, at 17:36, Kirill Peskov wrote:
> Due to some project restrictions I have to combine sources from 3
> repositories (1 Subversion and 2 Git repos), is there an easy way to
> achieve that in a declarative pipeline? Neither project subdirs nor
> files in the root of each repo are
I'd guess it is within the Subversion plugin.
https://github.com/jenkinsci/subversion-plugin/blob/41aea99bad1368d23092d6dbf41c7cdaadb85283/src/main/java/jenkins/scm/impl/subversion/SubversionSCMSource.java
четверг, 8 июня 2017 г., 12:24:30 UTC+2 пользователь David Aldrich написал:
>
> Hi Oleg
Hi Oleg
Thanks for your reply. To fix the immediate problem I think we just need some
additional GUI fields for the Multibranch Pipeline job. Is that in the scope
of the svn plugin or of the pipeline job type?
(Just wondering if someone can do it without being an svn expert).
BR
David
I don' t think the Jenkins CRON spec has seconds resolution.
You can build an orchestrater job that is scheduled to run every 1 minute.
Then in that job, loop 6 times with a sleep of 10 seconds and build another
job.
Also use the do not allow concurrent builds.
Something like this:
pipeline
The current state of the SVN plugin is discussed here:
https://groups.google.com/forum/#!topic/jenkinsci-dev/JUAzYLfuMhw .
Effectively the plugin has no active maintainer. So I would not expect any
ETA for this fix.
There are many pending changes
HI,
Jenkins 2.7.3
Performance Plugin 3.0
When I create a Relative Constraint in expert mode, using Average REsponse
time, the %'s I enter into the 'Tolerance' field do not get interpreted
correctly.
If I enter 5, the average response time threshold gets calculated as 50%
If I enter 1, the
Hi there,
On Thu, 8 Jun 2017, at 11:34, Eberhard Beilharz wrote:
> I'm using https://updates.jenkins-ci.org/stable/update-center.json as
> URL for the update site.
>
> When I check the JSON that gets returned from the update site I see that
> it contains the favorite plugin in version 1.16
Hi,
I recently received a message that there's an update for the Favorite
Plugin to version 2.3.0 to fix security vulnerabilities. When I went to
my Jenkins instance I saw version 2.2.0 of the plugin on the Update
page, but noticed that the last time Jenkins got the list of available
updates
Currently, as the test tools and debian packager are significantly
smaller than main source code I could probably stash/unstash their
corresponding subfolders to achieve the necessary effect, but it doesn't
look elegant... ;)
//...
git url:'url-to-packager-sources'
stash name: "debian-installer",
I have a properties file with the definitions:
https://github.com/SimonMatthews-BP/BPWarnings/blob/master/src/main/resources/hudson/plugins/warnings/parser/Messages.properties
Simon
On Wednesday, June 7, 2017 at 10:51:10 PM UTC-7, slide wrote:
>
> They are defined by creating a properties file
39 matches
Mail list logo