Comments (7)
There's $REPOSITORY (for the path of reprepro) vs. $REPOS (for the Codename as used inside $REPOSITORY/conf/distributions) but I don't see $REPOS re-used, so I'm not sure I fully understand what you're proposing. Any chance you could provide a PoC/patch?
from jenkins-debian-glue.
When I build a "release" package, package is uploaded in $REPOSITORY/release/$release
and $release
is also used in conf/distribution
as codename.
What I would like to do is upload package in repo $REPOSITORY/release/$release
but use $distribution
(like wheezy, squeeze, precise, ..) in conf/distribution
.
Maybe I'm doing something wrong but I don't see what.
Will try to provide PoC/patch.
from jenkins-debian-glue.
My bad. Everything happens in /usr/bin/build-and-provide-package
and specifically in function release_repos line 614.
I really think we should use ${distribution}
there. I'll work on a patch :)
from jenkins-debian-glue.
This is done to have multiple packages of the same release to be placed in the same repo.
If we have to build large project with complicated build-deps this feature helps to use already built packages to satisfy build-deps of forthcoming package builds.
from jenkins-debian-glue.
@realloc and this should not change !
Lets' say:
- I backport Zabbix and I want to backport it for Debian Wheezy & Debian Squeeze
2.Currently, at least 2 versions are maintained: 2.0 & 2.2
With current organization, you have to manage 4 release repositories, one per software version per distribution.
Now, imagine that you use $distribution
as codename for $release
repository.
You now have only one repository per software to manage. In my example, only 2 repositories: one for Zabbix 2.0 and the other for Zabbix 2.2
That sounds more easy and, at least to me, more logical.
What about dependencies ? In fact, it does not change anything. You'll still have to package your library for each distribution you support and integrate them in repo, as for now.
from jenkins-debian-glue.
Is someone willing to work on an up2date patch for this issue?
from jenkins-debian-glue.
JFTR: I don't have any environment in usage where this situation applies and am quite out of the loop regarding this. Also we (sadly) don't have according tests which ensure that on such changes nothing breaks in existing setups, so right now it's hard for me to work on this in my current scarce spare time. But if anyone is wiling to work on this I'd be more than happy to accept well tested and detailled PRs . (If anyone is interested in getting this fixed maybe look into #155 as a starting point?)
from jenkins-debian-glue.
Related Issues (20)
- Source build fails after Git repo change HOT 5
- Permission problem - denied to create directory in fakeroot /etc/ HOT 1
- pbuilder-satisfydepends: line 29: Segmentation fault HOT 3
- Error: Architecture $arch as given to --architecture is not know. HOT 3
- gpgv: Can't check signature: No public key HOT 8
- The generate-reprepro-codename script is too restrictive HOT 2
- Combine common functionality in scripts/generate-{git|svn}-snapshot HOT 12
- add support for vendor profiles HOT 8
- Determine the architecture(s) during the source build for a dynamic matrix of architectures for the binary job HOT 3
- qemu-debootstrap: Sorry, I don't know how to support arch (mips64) HOT 1
- /etc/sudoers.d/jenkins file only provided by j-d-g pp plugin
- Reprepro root dir only created by j-d-g pp plugin HOT 1
- cowbuilder (update) doesn't care about the $DIST variable but $DISTRIBUTION HOT 1
- Please add a git archive method HOT 1
- generate-reprepro-codename seems to use SUDO_CMD superfluously HOT 2
- puppet: jenkins-debian-glue user setup is broken
- Failed Loading plugin Pipeline v2.6 (workflow-aggregator) HOT 6
- Preperation of orig.tar.gz with --git-overlay enabled HOT 5
- Consider migrating j-d-g to a group/organization-like project and clarify maintenance and support situation HOT 8
- Automatic puppet deployment is broken HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jenkins-debian-glue.