Project

General

Profile

News

Reportnet platform: Reportnet project is now private

Added by Antonio De Marinis about 2 months ago

In order to improve security and reduce that sensitive private information is leaked out from Taskman (e.g. BDR information about FGases) we have decided to make Reportnet Taskman project private.

It means that you can only see tickets if you login with your Eionet account.

CCA - Migration to Plone: New feature: inspect the relevant items portlets

Added by Ichim Tiberiu 6 months ago

We've added a new feature to allow editors an easier understanding of how a filtering portlet shows its items: left side of the portlet title there is a magnifier glass icon. When clicked, it will open a popup with an overview of all fields configured on the portlet. These are the same fields that are accessible on the portlet by going through the Compose page, but at a more convenient location.

CORDA: Check the new Agile Boards in CORDA wiki (1 comment)

Added by Iñaki Diaz de Cerio 7 months ago

Planned Tasks Agile Board

Four work packages (categories) have been created in order to clasify all the planned tasks:
  • Operation
  • Content management
  • User Uptake
  • Project Management

Personal Agile Board

Board with all the personal planned tasks. This dashboard is useful to have full control of the status of my scheduled tasks.

Helpdesk Agile Board

The CORDA helpdesk will be responsible of the incidence management services with the purpose of maintaining the platform and content in satisfactory operating condition. The helpdesk main tasks are systematic inspection, detection, and correction of incipient failures either before they occur or before they develop into major defects. Maintenance, including tests, measurements, adjustments, and parts replacement, performed specifically to prevent faults from occurring.

More information in: CORDA Wiki

Reportnet platform: Changes to ticket status: Feedback split into two

Added by Søren Roug almost 2 years ago

The "feedback" state has been confusing for several people and projects. It has been used to both indicate that further clarification was needed by the assignee, for example when a ticket was added but not clear to one of the parties involved (author or assignee).

It has also been used to indicate a final stage like "user acceptance" or demo where the EEA staff usually approves the final delivery and either assigns it back to developer or accepts it and close the ticket.

To solve the issue to easily identify these two quite different states, wr have now two states:

  • Needs clarifications. This clearly indicates that the ticket is blocked if clarifications are not provided.
  • Acceptance/demo. To be used when work done in ticket is kind of ready to be demonstrated and accepted. It has less urgency.

The tickets that were in feedback are automatically in "Needs clarifications".

This will help identify the tickets that ate blocked waiting clarifications and react to them quicker so that work partially done is not wasted.

IDM2 B-Team: Reorganising the Networking Tools project

Added by Alex Eftimie almost 2 years ago

Since all of these projects had the same Manager in Franz, and a very similar Delivery Team consisting of the same Eau de Web developers, tickets were moved into a single project called "Networking Tools" (former "Naaya" project on Taskman).

The process is ongoing and will require Developers, Reporters and Product owners to review the tasks that are in the Backlog, Queue or Abandoned.

The ultimate goal is to have a clean queue with no more than two in progress tasks per assignee.

E-PRTR: Jenkins being migrated to CloudVPS

Added by Søren Roug almost 2 years ago

Last night we migrated Jenkins (http://ci.eionet.europa.eu/) to a new server on CloudVPS. It has also been installed as a Docker container. We did not migrate the history, so the build numbers are starting from one again. After a couple of check-ins, you'll have the five generation history you're used to. When I checked, none of the Java projects were able to build. Expect some build failures while they solve it.

The old server will be available at ci-old.eionet.europa.eu for a couple of weeks.

Reportnet platform: Jenkins being migrated to CloudVPS

Added by Søren Roug almost 2 years ago

Last night we migrated Jenkins (http://ci.eionet.europa.eu/) to a new server on CloudVPS. It has also been installed as a Docker container. We did not migrate the history, so the build numbers are starting from one again. After a couple of check-ins, you'll have the five generation history you're used to. When I checked, none of the Java projects were able to build. Expect some build failures while they solve it.

The old server will be available at ci-old.eionet.europa.eu for a couple of weeks.

Reportnet platform: First Dockerised services deployed in Production

Added by Søren Roug almost 2 years ago

Today we deployed our first Dockerised applications in production on the Public Cloud. They are the Art17Mapserver for the 2007 Art. 17 dataflow and the Transfer website. They are very small, but they are only the start. Of the traditional deployments we have migrated RDFdata, Semantic, Archiva, SVN, CR, ROD, DD, AclAdmin, HelpAdmin, Eionet CAS and WebQ1.

Reportnet platform: Migration of SVN service

Added by Søren Roug about 2 years ago

Yesterday after the last commit we migrated EEA's own SVN repository from the Falcon server that ran at our own location in Copenhagen to our new Cloud Service provider in Amsterdam called CloudVPS. The new repository is also called https://svn.eionet.europa.eu/

The migration should have no side-effect, but those of you who have used SVN since before 2012 might get prompted to accept the SSL certificate. It will look like this:

 Error validating server certificate for 'https://svn.eionet.europa.eu:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: *.eionet.europa.eu
 - Valid: from Oct  2 04:22:34 2012 GMT until Oct  4 05:14:11 2016 GMT
 - Issuer: GeoTrust, Inc., US
 - Fingerprint: 6B:F5:DC:6D:40:D8:7A:C9:38:23:DD:F9:4F:B8:05:4B:AB:06:0C:54
(R)eject, accept (t)emporarily or accept (p)ermanently?

The reason is that Falcon used a certificate that expired in 2012. Since you accepted permanently back then, the only check by the SVN client was whether the certificate had changed.

If you have any problems, send me an email.

(1-10/16)

Also available in: Atom