Hi Guys,
I have done some more work on the new Perforce plugin (see:
https://swarm.workshop.perforce.com/projects/p4-jenkins/files/main).
I hope that this now brings it up to the same level of features as the old one.
Please take a few minutes to skim through the user guide (there are lots of
I had a look at Bruno's plugin -- it looks like a great starting point for
what we need.
I think generalising Bruno's PBS Java API to support other similar systems
with qsub/qstat type commands should work well: it seems that a
PBSSlaveComputer could be generalised into a BatchSystemSlave.
Regard
On Wed, Jun 11, 2014 at 8:39 PM, Rob Terpilowski
wrote:
> I've created a class which [extends]
> AbstractProject.AbstractProjectDescriptor, and have annotated this
> class with the @Extension annotation. In addition I've added
> newJobDetail.jelly file to the project. However when I deploy the
Ping? Is there anyone available that can check my commit permissions or
suggest what I might be doing wrong? I'd really like to get this plugin
update released.
Thanks!
Randy
On Tuesday, June 10, 2014 1:13:16 PM UTC-7, Randy Coulman wrote:
>
> Hi, Jesse,
>
> Just tried again - no luck. I'm
On Wed, Jun 11, 2014 at 8:29 PM, 'Bruno P. Kinoshita' via Jenkins
Developers wrote:
> I thought about re-using the monitor-external-job plug-in
It makes for pretty weak integration since it does not let Jenkins
*initiate* the build. Cf.
http://developer-blog.cloudbees.com/2014/03/support-for-lon
What URL did you clone from and what error are you getting? If you are
using the ssh URL, do you have your key setup correctly? Are you using
Windows, *NIX, or Mac? Please give more details in the issue you are seeing.
On Thu, Jun 12, 2014 at 6:57 AM, wrote:
>
> Ping? Is there anyone available
I’m using SSH. I am able to push to my other GitHub repositories, so I
believe the key is set up correctly. Do I need a different key or
credentials for this repository?
I’m on a Mac, running OS/X 10.9.3.
Here is the error message I’m getting:
ERROR: Permission to jenkinsci/visualworks-store
Thank you Robert and Ben for your tips.
This is the closest I've been able to come to reproducing the form-based
authentication captured with wireshark.
curl -v -c cookies.txt http://localhost:8080/jenkins/
200 OK
curl -v -c cookies.txt -b cookies.txt
http://localhost:8080/jenkins/loginEntry
We'll need it in github before we can really do anything at all with it, so
that's still the first step.
Personally, I think it should be put into a separate branch within the
perforce-plugin repo, and have it publish to the beta update center under
the same namespace, though I admit some ignoranc
Please try again, I (re)added you as a committer for that repo.
On Thu, Jun 12, 2014 at 7:42 AM, wrote:
> I’m using SSH. I am able to push to my other GitHub repositories, so I
> believe the key is set up correctly. Do I need a different key or
> credentials for this repository?
>
> I’m on a Ma
It worked this time. Thanks so much for your help!
Randy
On Thu, Jun 12, 2014 at 8:48 AM, Slide wrote:
> Please try again, I (re)added you as a committer for that repo.
>
>
> On Thu, Jun 12, 2014 at 7:42 AM, wrote:
>
>> I’m using SSH. I am able to push to my other GitHub repositories, so I
>
On Thu, Jun 12, 2014 at 11:13 AM, Rob Petti wrote:
> publish to the beta update center under
> the same namespace, though I admit some ignorance as to how that would work
> with the release plugins and tagging.
I think everything would “just work” if (1) the new code is in a
branch such as ‘v2’,
Hi there,
I have successfully released my plugin also a day ago and the release does
show up in Jenkins Update
Center https://updates.jenkins-ci.org/download/plugins/elasticbox/.
However, the plugin ElasticBox doesn't show up in the list of available
plugins in Manage Plugins page of Jenkins s
Has your Jenkins server contacted and received the update list? If not,
then it won't show up in the update center.
On Thu, Jun 12, 2014 at 9:39 AM, Phong Nguyen Le wrote:
> Hi there,
>
> I have successfully released my plugin also a day ago and the release does
> show up in Jenkins Update Cent
A good test to see if jenkins properly recognizes the container role is if
it does not offer a delete option next to the role in the matrix security
config.
Also, looks like you're trying form based and trying to get curl to store
the session cookie. You might try basic auth instead.
Out of curio
If login through gui works OK then try token based [1] and see if that
works.
Other than that I am stumped.
[1]
https://wiki.jenkins-ci.org/display/JENKINS/Authenticating+scripted+clients
On Jun 12, 2014 12:53 PM, "Ben Castellucci" wrote:
> A good test to see if jenkins properly recognizes the
Ha ha ha ok, sorry, you already tried that link I sent.
(Sigh)
Maybe try again after you confirm success through the gui?
When I do this it's against jenkins deployed to weblogic. I use a
deployment plan to transform web.xml to add CLIENT-CERT to auth config and
then configure the security realm
Yes, it has. I even had forced refreshing of the update list in the
Advanced tab.
Thanks,
Phong
On Thursday, June 12, 2014, Slide wrote:
> Has your Jenkins server contacted and received the update list? If not,
> then it won't show up in the update center.
>
>
> On Thu, Jun 12, 2014 at 9:39 AM,
> How hard do you think it would be to make the PBS api generic to
>multipleschedulers, to support SGE and LL as well?
Not so hard I think. I used an existing API [1] as reference (first contacted
the author to see if we could re-use his library), and had a look at the Python
API too [2].
If
It shows up now finally and magically. Thanks for your help.
Phong.
On Thursday, June 12, 2014 10:40:34 AM UTC-7, Phong Nguyen Le wrote:
>
> Yes, it has. I even had forced refreshing of the update list in the
> Advanced tab.
>
> Thanks,
> Phong
>
> On Thursday, June 12, 2014, Slide wrote:
>
>>
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/security/SecurityListener.java#L91
I am trying to call that method in github-oauth-plugin after user is
authenticated
https://github.com/jenkinsci/github-oauth-plugin/blob/master/src/main/java/org/jenkinsci/plugins/Gith
On 12.06.2014, at 18:07, Jesse Glick wrote:
> just merge to master, change
> 2.0-beta--SNAPSHOT to 2.0-SNAPSHOT, and release
And maybe indicate incompatibility of existing configurations.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
2.0 should be indicate it, but the additional entry on Wiki is required to
explicitly describe the situation.
However, the 1.x version is not dead. I'm not sure about the behavior for
common update centers if the 2.x version goes to the main repo.
2014-06-12 23:58 GMT+04:00 Daniel Beck :
>
> On
Thanks,
That is great!
Peter
On Wed, Jun 11, 2014 at 5:38 PM, Ognjen Bubalo
wrote:
> Thanks for your time Dominik!
>
> I made the release. It should be visible soon.
>
>
> On Wed, Jun 11, 2014 at 10:04 PM, Dominik Stadler
> wrote:
>
>> Hi,
>>
>> I have now merged the changes and verified tha
I noticed a bug in the Jenkins MSTest plugin, and after some digging I
found that a pull request was submitted on Aug 30th 2013 with the fix. Is
there some way to expedite that request?
https://github.com/jenkinsci/mstest-plugin/pull/2
Thanks,
-Ian
--
You received this message because you are
Can you verify it builds correctly with that merged in? It looks like
buildhive built it and it failed, though I can look at the failure because
buildhive doesn't exist...
On Jun 12, 2014 6:21 PM, "iansul" wrote:
> I noticed a bug in the Jenkins MSTest plugin, and after some digging I
> found tha
Hi Jesse,
I will probably read the FlyweightTask javadoc&src and will experiment with it.
But that special project type could work too. Any chance to see an Open Source
version of it this year? :-)
Thanks!
Bruno
>
> From: Jesse Glick
>To: jenkinsci-dev@googl
Hello James
>Regarding the problem of Jenkins going offline, my feeling would be to
>mitigate this risk by: (1) Warning and doing a qdel on all Jenkins-submitted
>jobs when Jenkins shuts down cleanly. (2) Warning and doing a qdel on all
>lingering Jenkins jobs when Jenkins comes back up after a
1.553.1 rc1 posted at their usual locations: http://jenkins-ci.org/stable-rc
2014-06-11 10:13 GMT-07:00 ogondza :
> Backporting is over. We are ready for RC.
>
>
> --
>
> oliver
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To
29 matches
Mail list logo
