tigase/_clients/stork

tigase-mobilemessenger - Build # 1456 - Failure! (#213)

Activities

Tigase Support opened 8 years ago

Due Date
2017-05-28

tigase-mobilemessenger - Build # 1456 - Failure:

Check console output at http://build.tigase.org/jenkins/job/tigase-mobilemessenger/1456/ to view the results.

Changes:

No changes

Started by: Started by upstream project "tigase-jaxmpp2" build number 1,733

[...truncated 8.66 KB...]
[INFO] Tigase Android Messenger
[INFO] mobile-commons
[INFO] mobile-core
[INFO] mobile-phone-pro
[INFO] Tigase Android Messenger - Documentation
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Tigase Android Messenger 1.6-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ tigase-mobile ---
[INFO]                                                                         
[INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[INFO] Forking mobile-commons 1.6-SNAPSHOT
[INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Downloading: http://maven.tigase.org/tigase/jaxmpp-core/2.1.0-SNAPSHOT/jaxmpp-core-2.1.0-SNAPSHOT.jar
Downloading: http://maven.tigase.org/tigase/jaxmpp-android/2.1.0-SNAPSHOT/jaxmpp-android-2.1.0-SNAPSHOT.apklib
Downloading: http://build.xmpp-test.net/maven/tigase/jaxmpp-core/2.1.0-SNAPSHOT/jaxmpp-core-2.1.0-SNAPSHOT.jar
Downloading: http://build.xmpp-test.net/maven/tigase/jaxmpp-android/2.1.0-SNAPSHOT/jaxmpp-android-2.1.0-SNAPSHOT.apklib
[WARNING] Failed to getClass for org.apache.maven.plugin.javadoc.AggregatorJavadocReport
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Notifying upstream projects of job completion
Join notifier requires a CauseAction
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Tigase Android Messenger .......................... FAILURE [0.882s]
[INFO] mobile-commons .................................... SKIPPED
[INFO] mobile-core ....................................... SKIPPED
[INFO] mobile-phone-pro .................................. SKIPPED
[INFO] Tigase Android Messenger - Documentation .......... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 21.621s
[INFO] Finished at: Sat May 27 01:50:28 CEST 2017
[INFO] Final Memory: 22M/293M
[INFO] ------------------------------------------------------------------------
Waiting for Jenkins to finish collecting data
[ERROR] Failed to execute goal on project mobile-commons: Could not resolve dependencies for project tigase:mobile-commons:apklib:1.6-SNAPSHOT: The following artifacts could not be resolved: tigase:jaxmpp-core:jar:2.1.0-SNAPSHOT, tigase:jaxmpp-android:apklib:2.1.0-SNAPSHOT: Could not find artifact tigase:jaxmpp-core:jar:2.1.0-SNAPSHOT in tigase (http://maven.tigase.org) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :mobile-commons
[JENKINS] Archiving /var/lib/jenkins/jobs/tigase-mobilemessenger/workspace/mobile-commons/pom.xml to tigase/mobile-commons/1.6-SNAPSHOT/mobile-commons-1.6-SNAPSHOT.pom
[JENKINS] Archiving /var/lib/jenkins/jobs/tigase-mobilemessenger/workspace/mobile-documentation/pom.xml to tigase/mobile-documentation/1.6-SNAPSHOT/mobile-documentation-1.6-SNAPSHOT.pom
[JENKINS] Archiving /var/lib/jenkins/jobs/tigase-mobilemessenger/workspace/mobile-phone-pro/pom.xml to tigase/mobile-phone-pro/1.6-SNAPSHOT/mobile-phone-pro-1.6-SNAPSHOT.pom
[JENKINS] Archiving /var/lib/jenkins/jobs/tigase-mobilemessenger/workspace/pom.xml to tigase/tigase-mobile/1.6-SNAPSHOT/tigase-mobile-1.6-SNAPSHOT.pom
[JENKINS] Archiving /var/lib/jenkins/jobs/tigase-mobilemessenger/workspace/mobile-core/pom.xml to tigase/mobile-core/1.6-SNAPSHOT/mobile-core-1.6-SNAPSHOT.pom
channel stopped
[workspace] $ /bin/sh -xe /tmp/jenkins3109152709157842031.sh
+ export NIGHTLIES_DIR=/home/jenkins/nightlies
+ export DIST_DIR=/home/jenkins/nightlies/dists/
+ export COMPONENT=tigase-mobilemessenger
+ export DOCU_DIR=/home/documentation/tigase-mobilemessenger/snapshot
+ [ -e docs/ ]
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Notifying upstream projects of job completion
Email was triggered for: Failure - 1st
Email was triggered for: Failure - Any
Trigger Failure - Any was overridden by another trigger and will not send an email.
Trigger Failure - Still was overridden by another trigger and will not send an email.
Sending email for trigger: Failure - 1st

Applicable version: git/master

jaxmpp-core-2.1.0-20140808.150716-547.jar

Andrzej Wójcik (Tigase) commented 8 years ago

I have no idea if and how to fix it. We could change Jaxmpp version from 2.1.0-SNAPSHOT to 2.1.0, but I'm not sure if there is a point to do so if the new version is close to being released.

Bartosz Małkowski commented 8 years ago

It seems Jenkins try to build old Messenger, from branch "stable" instead of "master".

Wojtek, would you like to reconfigure Jenkins to use branch "master"?

wojciech.kapcia@tigase.net commented 8 years ago

Andrzej Wójcik wrote:

I have no idea if and how to fix it. We could change Jaxmpp version from 2.1.0-SNAPSHOT to 2.1.0, but I'm not sure if there is a point to do so if the new version is close to being released.

%andrzej.wojcik , %bmalkow

What's curious is why those snapshots are not visible though it seems they are there:

http://maven-repo.tigase.org/#artifact~snapshot/tigase/jaxmpp-core

http://maven-repo.tigase.org/repository/snapshot/tigase/jaxmpp-core/

At any rate - the "cost" of having it built correctly is relatively small and newer version is still not finished and this is still a "stable" release so I've update the dependencies and it's now fixed.

Bartosz Malkowski wrote:

It seems Jenkins try to build old Messenger, from branch "stable" instead of "master".

This is correct and it's configured like that: http://build.tigase.org/jenkins/job/tigase-mobilemessenger/configure

We have separate job for Messenger v3: http://build.tigase.org/jenkins/job/tigase-mobilemessenger-3/

(not sure why the division but judging from the build count it was setup almost 1,5 year ago)

Wojtek, would you like to reconfigure Jenkins to use branch "master"?

You have admin account on Jenkins as well ;-)

Andrzej Wójcik (Tigase) commented 8 years ago

I tried to download dependencies from Archiva and got 404, ie. http://maven-repo.tigase.org/repository/snapshot/tigase/jaxmpp-core/2.1.0-SNAPSHOT/jaxmpp-core-2.1.0-20140808.150716-547.jar (latest SNAPSHOT for 2.1.0 for @jaxmpp-core@).

It looks like someone deleted jar and Archiva was not aware of that!

wojciech.kapcia@tigase.net commented 8 years ago

Eric, have you deleted those files or have a file that do so periodically?

Eric Dziewa commented 8 years ago

The only thing I delete on the build machine are old nightlies. That file can be found on the backup machine.

wojciech.kapcia@tigase.net commented 8 years ago

Eric Dziewa wrote:

The only thing I delete on the build machine are old nightlies.

But you migrated build - is that correct?

That file can be found on the backup machine.

Where exactly? is it possible that paths changed or something and archiva has in it's index old path?

Eric Dziewa commented 8 years ago

Wojciech Kapcia wrote:

Eric Dziewa wrote:

The only thing I delete on the build machine are old nightlies.

But you migrated build - is that correct?

Have not migrated build machine.

That file can be found on the backup machine.

Where exactly? is it possible that paths changed or something and archiva has in it's index old path?

I have not touched Archiva only once months ago when the program wouldn't start. And all I did was start it.

Here is one of the latest I found, it's attached.

./2017-05-25/var/lib/jenkins/.m2/repository/tigase/jaxmpp-core/2.1.0-SNAPSHOT/jaxmpp-core-2.1.0-20140808.150716-547.jar
[root@backup build.xmpp-test.net]# pwd
/backup/build.xmpp-test.net

wojciech.kapcia@tigase.net commented 8 years ago

Eric, Archiva uses different paths (@/home/maven/repository@ and @/home/maven/repository-release@). At any rate - switching to latest release fixed the issue so I'm closing it.

Type	Bug
Priority	Normal
Assignee	wojciech.kapcia@tigase.net
RedmineID	5576
Spent time	5h

Issue Votes (0)

Watchers (0)

Reference

tigase/_clients/stork#213