View Issue Details

IDProjectCategoryView StatusLast Update
0011142Buildsyscommunity buildsyspublic2016-07-28 12:06
Reportermrunge 
PrioritynormalSeverityfeatureReproducibilityalways
Status resolvedResolutionfixed 
Summary0011142: create build tags for opstools sig
Descriptionplease create tags for opstools sig to be able to build packages
something like
 
opstools-candidate
opstools-el7-build
opstools-release
opstools-testing
Additional InformationOpstools uses ruby, java, node.js, golang (1.5), and python. I'm quite unsure about supporting other architectures than x86_64 yet.
TagsNo tags attached.

Activities

kbsingh@karan.org

kbsingh@karan.org

2016-07-12 15:06

administrator   ~0027045

can you elaborate on what opstools-el7-build would map to ? typically SIGs just use candiate/testing/release.

Also, i think we will need to qualify the tag's a bit more to be in line with the cbs convention.
mrunge

mrunge

2016-07-20 05:25

reporter   ~0027096

I just just copied the tags from cloud7-openstack.

Probably -build is the same as -candidate, since we don't want to inherit a build root from other tags (other than base os)
alphacc

alphacc

2016-07-20 06:57

developer   ~0027097

Hi,

-build is the "buildroot tag" use, by mock, for building. Nothing related to final tags.

They always exist.

kbsingh, let me know if I can proceed.

Thomas.
alphacc

alphacc

2016-07-20 07:00

developer   ~0027098

PS : I just need the sig name the rest is formatted by the script :-)
rmeggins

rmeggins

2016-07-22 13:08

reporter   ~0027109

Do we also need an opstools repo, or is that created automatically?
mrunge

mrunge

2016-07-22 13:11

reporter   ~0027110

The sig is named opstools
kbsingh@karan.org

kbsingh@karan.org

2016-07-26 13:12

administrator   ~0027125

can we list of the proposed tag's after the conversation earlier in the centos-devel irc channel ?
mrunge

mrunge

2016-07-26 18:19

reporter   ~0027130

as discussed earlier on irc:

opstools7-sensu-023
opstools7-common
opstools7-elastic-2
opstools7-perfmon-26
kbsingh@karan.org

kbsingh@karan.org

2016-07-27 12:53

administrator   ~0027137

+1
alphacc

alphacc

2016-07-28 12:04

developer   ~0027151

Hi All,

Tags are ready.

A list of available targets, buildroots, and default destination tags can be checked :

$ cbs list-targets | grep opstools
opstools7-common-el7 opstools7-common-el7-build opstools7-common-candidate
opstools7-elastic-2-el7 opstools7-elastic-2-el7-build opstools7-elastic-2-candidate
opstools7-elastic-common-el7 opstools7-elastic-common-el7-build opstools7-elastic-common-candidate
opstools7-perfmon-common-el7 opstools7-perfmon-common-el7-build opstools7-perfmon-common-candidate
opstools7-sensu-023-el7 opstools7-sensu-023-el7-build opstools7-sensu-023-candidate
opstools7-sensu-common-el7 opstools7-sensu-common-el7-build opstools7-sensu-common-candidate

This is what we discussed with the additional -common per project that are created automatically. No need to use it if not needed. But with the experience we see it can become useful quickly.

You can check inheritance on the koji web interface i.e :
https://cbs.centos.org/koji/taginfo?tagID=881

SIG members should request "sig-optools" group membership through https://accounts.centos.org/group/view/sig-opstools.

Then (cronjob need to pick-up changes so give it 15min) run :
$ cbs list-permissions --mine

You should have : build, build-opstools

mrunge, please confirm you can build something, otherwise please reopen this ticket.

--
Thomas

Issue History

Date Modified Username Field Change
2016-07-07 19:39 mrunge New Issue
2016-07-12 15:06 kbsingh@karan.org Note Added: 0027045
2016-07-20 05:25 mrunge Note Added: 0027096
2016-07-20 06:57 alphacc Note Added: 0027097
2016-07-20 07:00 alphacc Note Added: 0027098
2016-07-22 13:08 rmeggins Note Added: 0027109
2016-07-22 13:11 mrunge Note Added: 0027110
2016-07-26 13:12 kbsingh@karan.org Note Added: 0027125
2016-07-26 18:19 mrunge Note Added: 0027130
2016-07-27 12:53 kbsingh@karan.org Note Added: 0027137
2016-07-28 12:04 alphacc Note Added: 0027151
2016-07-28 12:04 alphacc Status new => resolved
2016-07-28 12:04 alphacc Resolution open => fixed