Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Autobuild branch selection isn't robust

Description

I configured autobuild with cdap branch 'spark-sink'.
There's also another branch with branch 'feature/spark-sink'.

When the cluster provisioned, the commit in the /data/git/cdap directory corresponded to the one from feature/spark-sink.
Perhaps this has to do with some name-matching bug in the git chef resource.

Release Notes

None

Activity

Show:

Ali AnwarSeptember 16, 2016 at 12:45 AM

I tried the steps again, and was still not able to reproduce it.
I also tried the reverse (configuring feature/spark-sink), and that also worked as expected.

Chris GianelloniSeptember 15, 2016 at 11:53 PM

It may have been an issue with the older Chef we used, or possibly even a bad version of git that's been patched. Glad to hear that is no longer an issue.

Ali AnwarSeptember 15, 2016 at 11:31 PM

I tried out what was described in the description section, and was not able to reproduce it.
Resolving it as such.

Chris GianelloniAugust 11, 2016 at 3:13 PM

We have switched from Chef 11 to Chef 12 since this was reported. Can you verify that this still happens with the newer Chef? If so, we'll have to file a bug upstream to get it fixed.

Cannot Reproduce
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Priority

Created March 25, 2016 at 1:53 AM
Updated September 16, 2016 at 12:45 AM
Resolved September 15, 2016 at 11:31 PM