Well it's faster has bigger RAM and more CPU.
I try to downgrade lots of version and I stop at version 1.501 this version
is working fine.
But I have problem that jenkins can't read build files because he's missing
plugin free-style-build.
Here is stacktrace from log: http://pastebin.com/yx14y
Here's the Jenkins job: https://ci.jenkins-ci.org/job/infra_release.rss/
Here's the Groovy script: https://github.com/jenkinsci/backend-release.rss
On 14.11.2013, at 23:12, Kevin Fleming (BLOOMBERG/ 731 LEXIN)
wrote:
> Where does this live? I'd like to improve it a bit.
>
> --
> You received
With a public Maven project, it is important that the declared dependencies
are available from a public repository, so that your project can be
effectively shared, forked, and built by curious, anti-social engineers
like me. Luckily, as Jesse stated, there is a relatively simple path for
you to bec
Regarding
https://github.com/jenkinsci/jenkins/commit/7828dcb46d9a18f88cc8e71046edc9ee91ed95e6,
I also propose to revert this commit in master and pick it to another
branch (e.g. to translation_ru).
I'll have some time to review changes on the next week. Roman, would you
like to participate in ver
On Thu, Nov 14, 2013 at 9:05 PM, Greg Peters wrote:
> Do I need another repository just to host this artifact?
You say it is decoupled from the plugin for possible reuse, so it
should be published to Central via OSSRH.
--
You received this message because you are subscribed to the Google Groups
I have other artifacts (which I coded) that are not in nexus or any other
public maven repository. I want to use one the these "service" artifacts
with my plugin but I'm not sure how the release will work.
1) I'm guessing the perform:release will package the .jar artifact inside
the plugin hpi?
Where does this live? I'd like to improve it a bit.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more op
OK, I quickly checked
https://github.com/jenkinsci/jenkins/commit/9c7f83659dcf506e27ddbfb72e354f1f96e6bce0
.
My opinion is that the content there is basically not adding much value.
IMO most of the time, it's actually replacing existing translation that was
already correct.
I even saw some contradi
On Thu, Nov 14, 2013 at 3:13 PM, Marco Miller wrote:
> 4. thread-B recreates the symlink, but that throws our hereby exception,
> given 3. (problematic).
Yeah, could happen.
> "On some operating systems it may not be possible to remove a file when it
> is open and in use by this Java virtual mac
Hi!
Some Jenkins instances of ours do log FileAlreadyExistsException-s from
time to time:
java.nio.file.FileAlreadyExistsException: (path2onesJob)/lastSuccessful
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:88)
(..) at *hudson.Util.createSymlinkJava7*(Util.java:1122)
(..)
hi,
have anybody used the sloccount plugin.??
i have couple of doubts with which i am struggling
please let me know
regards
irfan
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails f
Hi,
Sorry should have taken time to look into this earlier. I'll have a look at
the french translation tonight to see what was submitted.
Baptiste
2013/11/14 Kohsuke Kawaguchi
>
>
> Thank you for looking into this. A similar issue was reported in en_UK
> locale, so it's clear that we have to
On 11/13/2013 11:58 PM, Luca Milanesio wrote:
We need to make some tests on the scalability of the events API because of:
1) need to monitor over 1000 repos (one call per repo ? one call for all ?)
2) by monitoring the entire jenkinsci org, 300 events could be not enough in
case of catastrophic
Is there anything different about the new machine? (Disk, memory, os setup,
etc.)
Richard
On Friday, November 15, 2013, Martin Zajíc wrote:
> Hi, guys
> I have two jenkins running on same machine I moved them to another machine
> and performance is really bad it takes 30s to load dashboard which
On 11/14/2013 09:54 AM, domi wrote:
I think this was an exception and we should treat it as a such…
Yes, I agree. And we were able to recover all the commits after all, so
I don't think we need to throw the baby out with the bath water.
Sure this could happen again but by doing some backup
I did not quite get what the default is… I think
per default no-one should have access to all repos, but he/she is able to grant
itself this rights.
/Domi
On 14.11.2013, at 19:02, Kohsuke Kawaguchi wrote:
>
> OK, so the flow would be:
>
> - Our IRC bot would put users into the "pre-approved"
OK, so the flow would be:
- Our IRC bot would put users into the "pre-approved" team, which by
itself doesn't grant access to any repositories, but is used to keep
track of who can add/remove themselves to other repositories.
- We'll improve http://jenkins-ci.org/account to allow people
I think this was an exception and we should treat it as a such…
Sure this could happen again but by doing some backups we should be fine. Maybe
we would better ask GH why they provide the feature to block forced pushes just
in there enterprise solution.
/Domi
On 14.11.2013, at 18:50, Kohsuke Kaw
A feature like this makes a lot of for a Git hosting service. Good to
see that we are neither the first nor the only one to cause a trouble
like this [1].
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=361707
On 11/12/2013 03:19 AM, Dariusz Łuksza wrote:
In CollabNet we already implemen
Hmm, I don't fully understand the Maven implication of such a setup, but
there's a whole lot more to switching canonical repositories from one
location to another than mass-updating pom.xml, such as communicating,
infra managing, pull requests, access control and backup, that I'm
pretty cert
Thank you for looking into this. A similar issue was reported in en_UK
locale, so it's clear that we have to revisit the process.
I still don't have good sense on the scope of the problem. I wonder if I
should roll them back, or should try to just fix them one by one?
On 11/12/2013 11:48
2013/11/14 Oleg Nenashev :
> I confirm that Russian translation is quite confusing
If by "confusing" you imply some items that look literally translated
from English as if by machine translation and thus don't sound right
in Russian, then yes, such things exist, but that isn't that bad, and
it was
https://issues.jenkins-ci.org/browse/JENKINS-20586 - first browser
page load for 1.532.1-RC1 triggers JSONException
On Wed, Nov 13, 2013 at 7:00 PM, Kohsuke Kawaguchi
wrote:
> See http://jenkins-ci.org/stable-rc
>
> I still need to look at the changelog to see how to generate the updated
> one.
Hi, guys
I have two jenkins running on same machine I moved them to another machine
and performance is really bad it takes 30s to load dashboard which is
insane and I don't know what could be the problem.
I have lastest version (1.539) from repositories for ubuntu.
Here is my thread dump: http:
Hello,
I confirm that Russian translation is quite confusing (we enforce English
localization for all users, but...).
In my opinion, the approach should be quite simple: All localization
changes should be reviewed by people, who know the target language.
It would be also useful to have automati
25 matches
Mail list logo