The autobuilder now has the ability to track tags defined by a user.
This means that someone can define a tag called "Missing Java" and tell
the builder to keep an eye out for the string "You must specify a valid
JAVA_HOME or JAVACMD". Anytime that string is seen in a job, the job
will be tagged.
This can be a very powerful tool for developers that are looking for a
common problem with a lot of sources. For example, I know there is a
common file that exists under Linux in /usr/include but has no business
being on Solaris. An appropriate patch to anything that uses this
include is known to me and should be simple to reapply the same style of
patch elsewhere. So I define a tag that looks out for errors relating to
that file in build processes.
I'm sure we can find other uses for tags but that's the use-case it was
coded for. Thanks to anilg/wavejumper for the suggestions.
An example tag can be seen here: http://builder.tajinc.org/?f=tags&id_tag=1
Cheers,
-Tim
PS: you are welcome to request an account on the autobuilder. You need
an account to be able to add new tags.
_______________________________________________
gnusol-devel mailing list
gnusol-devel@lists.sonic.net
http://lists.sonic.net/mailman/listinfo/gnusol-devel
