This is an automated email from the ASF dual-hosted git repository.

arm pushed a change to branch scheduled_tasks
in repository https://gitbox.apache.org/repos/asf/tooling-trusted-releases.git


    omit 31d91cc  Add the ability to schedule future jobs. Worker claim updated 
to not claim future tasks. Metadata and workflow status tasks can schedule 
themselves.
     add 71d78ad  Add support for Maven staging (repository.a.o) - using 4443 
Nexus 3 new version
     add 30968f3  Add the ability to schedule future jobs. Worker claim updated 
to not claim future tasks. Metadata and workflow status tasks can schedule 
themselves.
     add bef00c5  Add scheduled column for tasks, allow asf_uid to be passed in 
task arguments

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (31d91cc)
            \
             N -- N -- N   refs/heads/scheduled_tasks (bef00c5)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 atr/models/sql.py                    |   5 ++
 atr/server.py                        |  36 +++--------
 atr/storage/writers/distributions.py |  92 ++++++++++++++++++++++++---
 atr/tasks/__init__.py                |   6 +-
 atr/tasks/gha.py                     |   8 +--
 atr/worker.py                        | 118 ++++++++++++++++++++---------------
 6 files changed, 172 insertions(+), 93 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to