Hi there,
Just wondering if there is any new supported feature of testing Jenkinsfile,
aka pipelines, locally, if so, where can i find some examples/docs? I want to
get rid of the manual and tedious process of pushing changes to my repo then
look at the jebkibs job andsee whether it does what
Hi all,
I want to change the IP address of view build in notification message .What
have I do.It run only in local host:8080.I Want to change the address.
Thanks,
Kalirajan
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from
Hi Utsav - yes sorry about that - it hasn't been implemented yet.
There are a few tasks in progress that make this up:
https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=171=planning=JENKINS-40298=visible=JENKINS-38490
Some code has been merged to support some of this, but not
Check this page
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build#Launching+a+build+with+parameters
On Thu, Dec 8, 2016 at 4:28 PM wrote:
> Fine.
> May I know, how can we pass user information from Travis to Jenkins
> automatically.
> I can see the user
Fine.
May I know, how can we pass user information from Travis to Jenkins
automatically.
I can see the user info in Travis who caused the build.
On Thursday, December 8, 2016 at 3:09:40 PM UTC-8, slide wrote:
>
> i and ii are out of the scope of this mailing list, but there is the
> Mailer
i and ii are out of the scope of this mailing list, but there is the Mailer
plugin and email-ext plugin for iii as long as you can pass the user
information to the Jenkins job from Travis
On Thu, Dec 8, 2016, 15:51 wrote:
> I want to know to how can a user (User1) get
I want to know to how can a user (User1) get E-mail Notification, when he
does the following:
i) User1 commits changes to GitHub in a Repo (Repo1)
ii) A Build in Travis CI server gets triggered whenever any changes
committed to Repo1. This Build job in travis internally triggers jenkins
job
Jenkins 2.15 (production) and 2.19.4 (test box).
We're stumped. Our *successful* build of a Maven project is not showing any
test results report. The console output for the build shows:
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ ALCParser ---
[JENKINS] Recording test results
Thanks all
Is this jenkins job DSL and jenkins pipeline is same or different. Actually
i need to create pipeline for creating Docker RPM creation.Let me know your
suggestions.
Thanks
Venkat
On 7 December 2016 at 21:33, xwyxw wrote:
> [image: Boxbe]
Hi,
I've been experiementing trying to get some information which might give a
clue to the issues I'm having with my Windows slave.
It's rather confusing, since to start with it worked fine. and the errors
aren't consistent (looking for past logs I see an error with unstashing
which I don't
I have a project that poll's Git every 5 minutes and builds on changes
using the Git plugin in a pipeline job. The issue I'm having is that if
the build fails (inside of 5 minutes), the next poll causes another build.
I also had a situation where a build started but didn't finish within the
Hey all,
Is there a known way to be able to block a job from running on some node
ONLY IF there are other specified jobs running on that same node?
For example, pretend you have 2 different build jobs ( Master build and CI
build ), and two nodes with two executors Jenkins can assign jobs to.
Okanswering my own question in case others are facing this. For a
pretty typical use case, this shouldn't be this hard. I'm still hoping
that someone is able to point out something simple that I missing so that I
can avoid jumping through these hoops.
Here's what I've got working for
Thanks Christoph .
By adding timestamp to war file , now i am able to see all previous
artifacts on artifactory.
Thanks once again.
Regards,
Pradeep Goud
On Friday, December 2, 2016 at 1:24:02 PM UTC+5:30, Christoph Nenning wrote:
>
> Hi,
>
> it seems to me that your WARs always have same
Hello i'd like to know if in declarative pipeline there is a way to use
conditions like failure and/or success in a generic stage (example:
stage('build docker image)), the idea is to make the execution of a stage
(here building a docker image) conditional to the success or failure of the
Hi,
this code actually doesnt work in a Sandbox, because I´m not allowed to use
new XmlSlurper() or its method setErrorHandler()
import groovy.util.XmlSlurper
node ("master") {
stage ("1st Stage")
git url:
"ssh://g...@licdci01.mycompany.net:7999/cd/deployment-configs.git",
Hi all,
when starting to work with Pipelines a tested this simple script:
// should fail - nothing else
assert false
This caused my Pipeline Job to hang - so I have to kill it.
When writing more complex code I ran more than once into this "hanging
pipeline" problem - no output, no stactrace
On Thu, Dec 8, 2016 at 4:02 AM, Anusha Bilgi wrote:
> I would like to know if there could be any issues in using a 64bit Java 8 to
> run Jenkins LTS 2.19.
>
> The jre that comes along with the Jenkins 2.19 is a 32bit Java 8 which is
> slow and more importantly Jenkins
I am not able to approve a stage using blue ocean UI (when using the input
step). Neither it shows something like "Waiting for your approval" when an
approval is required.
So ideally I'd recommend using ssh-agent, though you may in that case need
to force the checkout credentials to be ssh variant to have consistent
behaviour.
And you may want to ensure that your pipeline doesn't go commit on anything
other than blessed branches... keep in mind PRs will have access
So at least for the branch-source variants I'm working on GitHub and
bitbucket updates to integrate with the new eventing subsystem in SCM API
2.0...
Not sure if that will help gitlab...
On Thursday, 8 December 2016, Daniel CABRERA
wrote:
> Thx for the link. well
Thx for the link. well this ticket was open on october and nobody is
working on it. Seams like we are at the bottom of the backlog
On 8 Dec 2016 8:07 PM, "Torsten Reinhard" wrote:
> Hi,
>
> using BitBucket (Server) I had the same problem. This is already adresses
> in
Hi,
using BitBucket (Server) I had the same problem. This is already adresses
in https://issues.jenkins-ci.org/browse/JENKINS-38447
Maybe the analysis in there may explain why it also doesn´t work for Gitlab.
Regards, Torsten
Am Donnerstag, 8. Dezember 2016 03:49:04 UTC+1 schrieb xwyxw:
>
>
I would like to know if there could be any issues in using a 64bit Java 8
to run Jenkins LTS 2.19.
The jre that comes along with the Jenkins 2.19 is a 32bit Java 8 which is
slow and more importantly Jenkins hangs during a restart and fails to boot
again unless java is manually killed.
Please
24 matches
Mail list logo