This idea is from @abayer, from these following tweets:
And:
We could simply add tags to builds, and then create some place that would list the builds (or other things) that are tagged appropriately. Or we could add a way to define which builds should be exported to some tool, and then via the plug-in API maybe, post to this external tool.
From https://code.google.com/p/build-pipeline-plugin/issues/detail?id=80
Jenkins Build Pipeline Plug-in, by Centrum Systems (Australia), is an excellent plug-in, used by many users (over 6000 downloads according to last report).
However, it does not work well with the Jenkins Promoted Builds Plug-in, another great plug-in (over 4100 downloads last month).
It means that users are not able to create pipelines based on promotion (promoted pipelines?). This contribution would be awesome, useful and help a lot of users (maybe over 10000? :-)
From https://groups.google.com/forum/?fromgroups=#!topic/stacks-users/2HwY2dDyeSM.
Stacks processes RAD DNA sequences and produces output, that is displayed on the Web with a bundled PHP+MySQL application. This application is quite useful, especially since it helps developers to analyze large amounts of data.
One limitation though, is that some management tasks may need manual execution of SQL’s in the database. Someone could add few scripts or new features to the Web interface (like a management section?). This could help researchers on their research.
Já existem projetos semelhantes, porém seria interessante uma solução um pouco modular, onde usuários pudessem escolher dicionários diferentes, bem como algoritmos também.
Exemplo: #caiunarede seria segmentado em [‘caiu’, ‘na’, ‘rede’].
Links uteis:
This idea happened after Andrew Gray’s objectified-solutions. With Objectified Solutions one can extract meta information from a .NET solution. This information includes:
The code is hosted at GitHub too. Maybe someone could even think about a “.NET solution project” job type for Jenkins.