You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tooling.apache.org by "dave2wave (via GitHub)" <gi...@apache.org> on 2026/01/05 20:27:27 UTC
[I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases)
dave2wave opened a new issue, #475:
URL: https://github.com/apache/tooling-trusted-releases/issues/475
There should be a compose policy field which is a yaml of tag to gitignore pattern matches.This mapping should be a default which tags files in certain subdirectories for distribution channels.
Something like:
```
maven:
- 'maven/**'
pypi:
- 'pypi/**'
dockerhub:
- `docker/**'
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases)
Posted by "alitheg (via GitHub)" <gi...@apache.org>.
alitheg commented on issue #475:
URL: https://github.com/apache/tooling-trusted-releases/issues/475#issuecomment-3780478049
I want to get it to work this way, if we can! But from what I can see rsync can only handle the gitignore patterns in "--include" and that maintains the source path, so if you pass "maven/**" you get a "maven" directory. Although I've just spotted we do a lot of parsing on the rsync command ourselves in ssh.py - do you think we could interpret the pattern in there and result in the right files?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases)
Posted by "alitheg (via GitHub)" <gi...@apache.org>.
alitheg closed issue #475: Allow files to be tagged in the compose phase according to a mapping
URL: https://github.com/apache/tooling-trusted-releases/issues/475
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #475:
URL: https://github.com/apache/tooling-trusted-releases/issues/475#issuecomment-3780108957
You should rsync the files into the root directory so that on the GH Runner they all are at the root level. I was looking for a rich setup, but if it is easier then we can define the subdirectories that must be used.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #475:
URL: https://github.com/apache/tooling-trusted-releases/issues/475#issuecomment-3719718713
Parallel work and obviously writing to _**dist**_ is the primary goal of this whole effort. There are a few more work issues to be added for the Beta.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #475:
URL: https://github.com/apache/tooling-trusted-releases/issues/475#issuecomment-3717218609
need to add ASF distribution = what is to be published to https://downloads.apache.org/ independently from third-party repositorie slike Maven Central, PyPI, Dockerhub, etc...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #475:
URL: https://github.com/apache/tooling-trusted-releases/issues/475#issuecomment-3773673641
#508 depends on accomplishing this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases)
Posted by "alitheg (via GitHub)" <gi...@apache.org>.
alitheg commented on issue #475:
URL: https://github.com/apache/tooling-trusted-releases/issues/475#issuecomment-3785751404
Closed by #579
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases)
Posted by "alitheg (via GitHub)" <gi...@apache.org>.
alitheg commented on issue #475:
URL: https://github.com/apache/tooling-trusted-releases/issues/475#issuecomment-3779805933
I've started looking at this. I'm trying to do it with the rsync goal in mind as well. One thing I've run into is that in the example:
```
maven:
- 'maven/**'
pypi:
- 'pypi/**'
dockerhub:
- `docker/**'
```
Let's say I `rsync --include maven/**`, that's great, but now for example my maven files are going to be in potentially different locations/globs (one repo might use "maven/**" and another might use "java/**", and another might specify multiple patterns). That means the destination dir they sync to isn't predictable which makes it harder to run the njord repo build because I don't know where all my files are. I'm trying to update the deployment script to pull the tagging spec (from the endpoint added in 03dcb51) but it's proving cumbersome (and I'm concerned it may be brittle)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases)
Posted by "hboutemy (via GitHub)" <gi...@apache.org>.
hboutemy commented on issue #475:
URL: https://github.com/apache/tooling-trusted-releases/issues/475#issuecomment-3717349506
just found https://github.com/apache/tooling-docs/blob/main/apache-trusted-releases/svn-dist.md = what i called previously "ASF distribution"
I'd expect that "ATR writes to SVN - ATR Releases write to svn:dist/release as an interim step" is done before we work on "ATR writes to third party distributions"
@dave2wave can you confirm that's the plan?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org