Bug 12064 - [pyro-next] eclipse-plugin failing
Summary: [pyro-next] eclipse-plugin failing
Status: RESOLVED NOTABUG
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.3.2
Hardware: x86 Multiple
: Undecided critical
Target Milestone: 2.3.2
Deadline: 2017-09-08
Assignee: Ross Burton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-09-07 23:33 UTC by Armin Kuster
Modified: 2017-09-14 14:40 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Unknown (Hard to categorize)
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Armin Kuster 2017-09-07 23:33:30 UTC
no error I can find. I just aborts.

Is there something wrong with AB or am I picking the wrong branch?
the eclipse sources have branches listed as mars-pyro or mars/pyro this is confusing and should be cleaned up or the AB should pick the correct one for me.
Comment 1 Joshua Lock 2017-09-11 16:45:30 UTC

The branch name format is incorrect, it is confusing but that's a decision the eclipse-poky team made long ago.

The format is eclipse-release-name/poky-release-name, except for the master branch.

Looking at a failed build:
https://autobuilder.yoctoproject.org/main/builders/eclipse-plugin-neon/builds/304

it looks like the correct format was used for the Mars Eclipse plugin but not the Neon Eclipse plugin:

branch_eclipse-poky-mars 	mars/pyro 	Trigger
branch_eclipse-poky-neon 	neon-pyro 	Trigger
Comment 2 Ross Burton 2017-09-14 14:40:23 UTC
Closing as not a bug.  Bug 11804 is asking for convenience dropdowns so you don't need to remember all the branch names.