I see it as a better practice to have mails sent to everyone having
interest in the project's development.
But it is better to float such mails after we have a stable build.
Since we now have a CI instance, can we have a build that can list down
the quality of the project ? We have added some quality metrics eg
checkstyle to maven site plugin, but I am not sure when would that be
built. May be at the time of release ? But wouldn't that be late to do
any meaningful fixes.
@Matthias : please add my address to the notification list.
On 08-08-2012 10:51, Matthias Friedrich wrote:
Hi,
it's possible, I've seen documentation on the wiki. However, I've never
seen as many broken builds as on this Jenkins instance, so I'd like to
observe build stability for a week or two before we do this. Getting
spammed by lots of false positive warnings would be quite annoying.
Ping me again in a couple of weeks and I'll set it up if we agree that
we want it.
@Rahul: I can add your address to job notification for the time being
if you want.
Regards,
Matthias
On Tuesday, 2012-08-07, Josh Wills wrote:
Quite possibly. How do we do that?
On Tue, Aug 7, 2012 at 8:41 PM, Rahul <[email protected]> wrote:
Shouldn't mails from jenkins be sent to the dev list also ?
On 08-08-2012 01:38, Gabriel Reid wrote:
Thanks for getting that all set up Matthias!
Could you (or Josh, or anyone with the rights to do so) add my address
([email protected]) to the email notification list on the jobs (or grant me
editing rights)?
Thanks,
Gabriel
On Tuesday 7 August 2012 at 21:54, Matthias Friedrich wrote:
Hey guys,
we now have two Jenkins build jobs for Crunch:
* https://builds.apache.org/job/Crunch-master/
* https://builds.apache.org/job/Crunch-master-integration/
The first one runs "mvn package" on commit, the second one runs
"mvn verify" nightly. Apache's build farm seems to be overloaded
so I think it's better to be good citizens and not run our integration
tests on commit. If you want email notifications you can add your mail
address at the job configuration page (you need editing authorization
for this). Before taking this further towards producing reports, let's
see how stable the system is.
Thanks Josh and Brock for getting this started!
For people reading this mail on the archives: If you are using git and
get an error message "Could not apply tag ... Please tell me who you
are" then see INFRA-4697.
Jenkins wans to tag each build and that fails if git's user.email and
user.name (http://user.name) are missing. Some build machines are
properly set up, others
aren't, producing this error message. You can set these configuration
values in your Jenkins job config. In section "Build Environment",
activate checkbox "Set environment variables" and enter the following:
GIT_COMMITTER_NAME=Jenkins
[email protected] (mailto:[email protected])
Good luck :)
Regards,
Matthias
