I see instructions at [1] for how one should be able to trigger a build.
However I have a secured Jenkins and visiting the URL on my site results in
a stack trace unless I'm logged in. Do I need to give anonymous some
permissions? I'm using project based matrix authorization and anonymous has
read
27;s the behaviour that I have working in the instance I run so your
> issue might be an "unrelated" one...
>
> Richard.
>
>
> On Tue, Jun 25, 2013 at 2:26 PM, Jon Schewe wrote:
>
>> I see instructions at [1] for how one should be able to trigger a build.
>&
I just reconfigured my Jenkins to be behind apache so that it's on port 80
and SourceForge will let me hit it and now the nofityCommit hook works.
Perhaps something about being exposed on an alternate port?
On Tue, Jun 25, 2013 at 5:44 AM, Jon Schewe wrote:
> Here's what I g
I just upgraded to LTS version 1.509.2 and found that I'm sing the SSH
Credentials Plugin version 0.2 that has this bug[1]. The bug report says
to upgrade to 0.3. When I look at the update center version 1.4 is the only
version available and I get a warning that it's not compatible with my
version
i-users@googlegroups.com]
> on behalf of Jon Schewe [jpsch...@mtu.net]
> *Sent:* Wednesday, October 09, 2013 1:44 PM
> *To:* jenkinsci-users
> *Subject:* How to get particular version of a plugin
>
> I just upgraded to LTS version 1.509.2 and found that I'm sing the SSH
>
I just installed this today to try and avoid some issues I have with locks
& latches. I have some multi-configuration jobs. I want to allow multiple
jobs to run at the same time, but only 1 job of a given category to run per
node. This sounds exactly like what the plugin was written for. So I went
ive any useful suggestions.
>
> Matthew
>
> ** **
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Jon Schewe
> *Sent:* 09 October 2013 20:10
> *To:* jenkinsci-users
> *Subject:* Problem with Throttle Con
I just upgraded to git plugin 2.0 and Jenkins 1.509.4. I wiped out my
workspace and then tried to run a build and got the messages below. I tried
turning on the option to wipe out the workspace and force a clone and that
didn't help either.
*15:56:31* Started by user Jon Schewe
<http:/
I got my job to build, here is what I did. Is everyone expected to do this
for all jobs using git?
1) Delete configured repository
2) Delete configured branches
3) Select "None" as SCM
4) Save
5) Configure git repository
On Thu, Oct 24, 2013 at 2:59 PM, Jon Schewe wrote:
> I jus
g/browse/JENKINS-20195
>
> Mark Waite
>
>
> On Thu, Oct 24, 2013 at 2:25 PM, Jon Schewe wrote:
>
>> I got my job to build, here is what I did. Is everyone expected to do
>> this for all jobs using git?
>>
>> 1) Delete configured repository
>> 2)
Also note that the Throttle Concurrent Build plugin appears to have some
problems with matrix jobs.
https://issues.jenkins-ci.org/browse/JENKINS-19986
On Tue, Nov 5, 2013 at 7:49 AM, Baptiste Mathus wrote:
> Hi,
> Just a quick note: for Jenkins, see here:
> https://wiki.jenkins-ci.org/display/
Anyone else running into problems with the git plugin version 2.0? I'm
using Jenkins 1.509.4 and have run into the problem that if I wipe out my
workspace either manually that the plugin can't clone a new workspace. It
errors like this:
*16:08:58* Started by user Jon Schewe
<h
at helps avoid the problem.
>>
>> If you're using include region, exclude region, or exclude user, then
>> you'll need to also add the "Force polling using workspace" option. The
>> default is now to use fast remote polling, but that default cannot proces
fast remote polling, but that default cannot process
> include or exclude regions.
>
> Mark Waite
>
>
> On Sun, Jan 5, 2014 at 7:12 PM, Jon Schewe wrote:
>
>> Anyone else running into problems with the git plugin version 2.0? I'm
>> using Jenkins 1.509.4 an
I was just looking at upgrading my Jenkins installs today. I have both on
LTS one is at 1.509.4 and one is at 1.509.2. However when I goto the manage
Jenkins page I don't see an upgrade available. When I look at
jenkins-ci.orgI see that 1.532.1 is available. Did something change in
how upgrades are
>>
>>>> If you're using include region, exclude region, or exclude user, then
>>>> you'll need to also add the "Force polling using workspace" option. The
>>>> default is now to use fast remote polling, but that default cannot process
>>>&g
Using 1.4.0, everything appears to work fine.
Using 2.0 I have the following problems:
If I manually delete the workspace using the Wipe out workspace link AND
have prune stale remote branches on, the plugin will not clone the
repository with the error:
*08:56:16* Started by user Jon Schewe
ot;, then later executions of that job may
> find that value of remote.origin.url and not report the exception. That
> won't help for the first run of the job after the workspace has been wiped,
> since the prune call happens before the first build step.
>
>
> On Tue, Jan 7, 2
. I've not seen any bug report like that in my looking at bugs
> related to the git plugin. Can you find a set of steps which make that bug
> repeatable, and then submit it as a bug?
>
>
> On Tue, Jan 7, 2014 at 7:00 AM, Jon Schewe wrote:
>
>> Using 1.4.0, everything
Looking at jenkins-ci.org I see that the latest LTS release is 1.532.2.
Looking at my Jenkins install I'm running 1.532.1. Going to the management
page for my Jenkins install I do not see the option to upgrade. I have
another Jenkins instance setup that is telling me there is an update
available. W
ugin metadata from the
> update center
>
>
> On 28 February 2014 15:36, Jon Schewe wrote:
>
>> Looking at jenkins-ci.org I see that the latest LTS release is 1.532.2.
>> Looking at my Jenkins install I'm running 1.532.1. Going to the management
>> page for my Jenkins i
e the page
was loaded over https, but was requesting an insecure page over http. Once
I changed the update center URL to be https, then I see updates.
On Fri, Feb 28, 2014 at 10:03 AM, Jon Schewe wrote:
> So Jenkins doesn't do the polling on it's own?
>
>
> On Fri, Feb 28, 2
reliance
>>>> on Sun internal code in the Hudson/Jenkins test framework. Builds fine
>>>> with java 6 and that should work on a java 7 runtime.
>>>>
>>> Yes, I managed to compiled the source code with JDK 6 and generate the
>>> hpi file in target foler... work
odified or had more option.
> However, at the end of the day, the important thing is if your jobs can be
> compiled, no matter how.
> Thank you Jon for your advice.
>
>
>
> On Tuesday, October 23, 2012 4:59:08 AM UTC+3:30, Jon Schewe wrote:
>
>> I build Qt based projects
I just switched one of my Jenkins servers to the LTS release. I downloaded
the war file and replaced my current war file. I then updated the update
site for the plugins and restarted. Everything is running fine, except when
I goto Manage Jenkins I'm still prompted to upgrade to the latest bleeding
Can you explain more? What link provided by Jenkins?
On Mon, Jan 7, 2013 at 8:09 AM, SBreitbach wrote:
> Don't use the link on the webpage. Use the link provided by Jenkins itself
> instead.
--
http://mtu.net/~jpschewe
Deleting the contents of the updates directory fixed it. Now I see the
option to get 1.480.2 instead of 1.496.
On Mon, Jan 7, 2013 at 1:29 PM, teilo wrote:
> you may waat to remove the contents of jenkins_dir/data/updates
>
> /James
>
>
> On Monday, 7 January 2013 13:53:
I just upgraded to 1.480.2 from 1.471 and my JNLP slaves can no longer
connect. I get an error:
JNLPException[category: Download Error : Exception: java.io.IOException:
Server returned HTTP response code: 403 for URL:
https://server:8010/computer/slave-jnlp/slave-agent.jnlp : LaunchDesc: null
]
i.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04
>
>
> 2013/1/7 Jon Schewe 'jpsch...@mtu.net');>>
>
>> I just upgraded to 1.480.2 from 1.471 and my JNLP slaves can no longer
>> connect. I get an error:
>>
>> JNLPException[category
I can't point you at any docs, but I've setup email-ext like I do for
regular jobs and I get one email for each multi-config job and one for the
overall job. I changed the template to put the logs in my email-ext emails
and each email contains the logs. I haven't tried putting test results in
the e
I just upgraded from 1.480.2 to 1.480.3 and most of my jobs disappeared.
Switching back to 1.480.2 brings all of my jobs back.
I see the following errors in my stdout log file:
Feb 20, 2013 10:05:03 PM hudson.model.Queue load
WARNING: Failed to load the queue file /home/hudson/.hudson/queue.xml
h
I've had this happen at least 3 times in the past month. I'm running LTS
(1.480.3) on java 1.6.0_26 on Debian. Has anyone else seen this?
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xb53cc357, pid=18932, tid=2976336752
#
# JRE version: 6.0_26-b03
#
omatically check out and build. The version number
> > changes everytime a tag is applied so if possible i would like to use
> > something like a regular expression. i.e. any tag that contains the
> > string %LIVE% should trigger a build.Is this possible with CVS
> > or
are
> written, common XML test output formats, and how reports are
> published.
>
> Thanks,
>
> -Ed
>
>
--
Jon Schewe | http://mtu.net/~jpschewe
to my developers would have the branch that was build.
Thanks.
--
Jon Schewe | http://mtu.net/~jpschewe
ing for an
> open source code coverage tool supported in Jenkins and Google test
> framework in windows platform.
>
> Any suggestion would be sincerely appreciated.
>
> Thanks in advance,
> Pank
>
>
--
Jon Schewe | http://mtu.net/~jpschewe
with multi-machine setups on multiple
> operating systems as I have here:
>
> http://jenkins.simplistix.co.**uk/job/testfixtures-buildout/<http://jenkins.simplistix.co.uk/job/testfixtures-buildout/>
>
>
> Why not just create a git repo with submodules for all of the other
repositories and then point Jenkins at that?
--
Jon Schewe | http://mtu.net/~jpschewe
at
com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
at
com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
at
com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
...
--
Jon Schewe | http://mtu.net/~jpschewe
ve my
jobs back again.
On Wed, Jul 11, 2012 at 2:12 AM, Ullrich Hafner wrote:
> Which version of analysis-core is installed? Which version of the dry
> plug-in did you install?
>
> Ulli
>
>
> On 07/11/2012 05:47 AM, Jon Schewe wrote:
>
> I just updated to jenkins 1.474 and
I use the email-ext plugin to send out emails about build failures. I
originally had it set to send email to all culprits when the build failed.
However I import some code from other repositories and then Jenkins wanted
to send emails to people that weren't on my development team because of
these i
On Tue, Apr 1, 2014 at 2:56 PM, Jon Schewe wrote:
>
>> I use the email-ext plugin to send out emails about build failures. I
>> originally had it set to send email to all culprits when the build failed.
>> However I import some code from other repositories and then Jenkin
Oh, that doesn't sound too bad. Can you point me at some documentation
and/or examples?
Thanks.
On Tue, Apr 1, 2014 at 5:23 PM, Slide wrote:
> No, you use Groovy for the pre-send script. There is no other plugin that
> I know of.
>
>
> On Tue, Apr 1, 2014 at 3:14 P
dr -> !addr.toString().contains('@
> baddomain.com') }
> msg.setRecipients(Message.RecipientType.TO, filtered)
>
> slide
>
>
> 1 - https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin
>
>
> On Fri, Apr 4, 2014 at 12:31 PM, Jon Schewe wrote:
>
>
ins('@
gooddomain.com') }
msg.setRecipients(javax.mail.Message.RecipientType.TO, filtered as
javax.mail.Address[])
On Fri, Apr 4, 2014 at 6:31 PM, Jon Schewe wrote:
> Awesome, thanks!
>
>
> On Fri, Apr 4, 2014 at 3:09 PM, Slide wrote:
>
>> Information from the wiki [1]
>&g
I read the documentation on setting up Jenkins behind Apache and finally
got rid of the warning about the reverse proxy being setup wrong. That was
fixed by putting my configuration for Jenkins directly inside the
VirtualHost directive. Once I did that, the warning went away. However now
I've got t
Never mind, I just found the answer:
https://groups.google.com/forum/#!topic/jenkinsci-issues/2s2DeNtpxwM
On Sat, Jul 12, 2014 at 10:56 PM, Jon Schewe wrote:
> I read the documentation on setting up Jenkins behind Apache and finally
> got rid of the warning about the reverse proxy being
I have the plot plugin generating plots from some of my test scripts. I'm
using the properties file format. So for each series that I want to graph I
create a file that contains YVALUE=. For instance I have a series
named "foo" and I create a file named "foo.properties" that contains a
single line
I see that under the advanced section of the compiler warnings module there
is an option to ignore files based on their absolute file path. Does this
work to filter warnings found in the console output or only when scanning
files?
I have a directory at the top of my workspace named "log4cxx/source
s to YVALUE or create a new file for each build? Is it
> difficult to write to the properties file in Javascript?
>
>
> On Monday, July 28, 2014 11:12:17 AM UTC-4, Jon Schewe wrote:
>
>> I have the plot plugin generating plots from some of my test scripts. I'm
>> usi
webpage performance over time).
>
> I apologize as I am new to all of this and am trying to piece it all
> together.
>
> On Monday, July 28, 2014 12:33:47 PM UTC-4, Jon Schewe wrote:
>
>> The "foo.properties" file is created for each build as part of my
>> con
creating a new foo.properties file for each
>> run or add a new value to YVALUE?
>>
>> On Monday, July 28, 2014 1:47:49 PM UTC-4, Jon Schewe wrote:
>>>
>>> That's how I use the plot plugin as well. Have your script write
>>> YVALUE=time into th
t;
>> So just to clarify, will I be creating a new foo.properties file for each
>> run or add a new value to YVALUE?
>>
>> On Monday, July 28, 2014 1:47:49 PM UTC-4, Jon Schewe wrote:
>>>
>>> That's how I use the plot plugin as well. Have your script
28, 2014 at 10:14 AM, Jon Schewe wrote:
> I see that under the advanced section of the compiler warnings module
> there is an option to ignore files based on their absolute file path. Does
> this work to filter warnings found in the console output or only when
> scanning files?
ined after the filter operation.
>
> But it should be possible to move the filtering after the expansion.
> Please file a new feature request in Jira.
>
> Am 28.07.2014 um 21:37 schrieb Jon Schewe :
>
> It seems that the problem is that the filter is not done on the absolute
Something else to be aware of. If this is a new branch there will be an
empty list of developers and culprits because the plugin only builds up a
list of authors on the list of changes. The list of changes comes from the
git plugin and on a new branch the list of changes is empty because it
can't d
I would suggest you look at the plot plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Plot+Plugin. If you're writing
the time to a file, it should be pretty easy to modify to write to a
properties file.
I had a discussion on the list a couple of weeks ago about how to this this
plugin up. You c
I tried logging into Jira today to update a ticket and got
Sorry, a communication error occurred while trying to contact the remote
authentication server.
Is anyone else having this problem or is it just me?
Jon
--
http://mtu.net/~jpschewe
--
You received this message because you are subscrib
It depends on what you want to do. I run my OSX slaves with the web start
and a login script. This allows my tests to interact with the window
manager. If you don't need that, then sticking with ssh is good. The only
downside I can see to the ssh setup is that you need to allow ssh on your
OSX mach
I'm trying to switch to using the pipeline plugin and I'm having a really
hard time finding documentation. In particular I want to call an ant build
script and I don't want to do it with sh/bat because the OS may change.
I found some documentation at [1], however I get errors about missing
propert
t; Either that, or we can insert that documentation into the Ant plugin wiki
> page (to match what is done for the withMaven step
> <https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin>)
>
> Mark Waite
>
> On Fri, Sep 22, 2017 at 8:25 PM Jon Schewe >
&g
Issue created at https://issues.jenkins-ci.org/browse/JENKINS-47076.
On Saturday, September 23, 2017 at 7:56:05 AM UTC-5, Jon Schewe wrote:
>
> Thank you for the pointers. Do you know how this documentation
> <https://jenkinsci.github.io/job-dsl-pl
On Sat, Sep 23, 2017 at 8:08 AM, Mark Waite
wrote:
>
>
> On Sat, Sep 23, 2017 at 6:56 AM Jon Schewe wrote:
>
>> Thank you for the pointers. Do you know how this documentation
>> <https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.helpers.step.Ste
On Sat, Sep 23, 2017 at 8:45 AM, Daniel Beck wrote:
>
> > On 23. Sep 2017, at 15:35, Mark Waite wrote:
> >
> > I think we can contribute to jenkins.io, even without edit access.
>
> The notable exception being generated pages, like everything in
> https://jenkins.io/doc/pipeline/steps/ -- period
Adding this to the copy artifact plugin page will help others. Those pages
are wikis so you can just login with your Jira credentials and edit.
On Fri, Oct 6, 2017 at 3:12 PM, dandeliondodgeball
wrote:
> Took me a while to find this, so posting it to make it easier to find.
>
> CopyArtifact synt
64 matches
Mail list logo
